# mangling include\_role path

**URL:** <https://forum.ansible.com/t/mangling-include-role-path/29737>\
**Category:** Ansible Project\
**Created:** [February 21, 2019, 10:01pm UTC](https://forum.ansible.com/t/mangling-include-role-path/29737 "2019-02-21T22:01:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dimon](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@Dimon](https://forum.ansible.com/u/Dimon)\
**Post date:** [February 21, 2019, 10:01pm UTC](https://forum.ansible.com/t/mangling-include-role-path/29737/1 "2019-02-21T22:01:57Z")

</div>

I’ve set up a playbook that includes another playbook located under ‘a/b/c’ subdirectory. From that included playbook I do ‘include\_role’ which fails since role is located at top level and not the sub-playbook level. What are the most common ways of mitigating this?

sample (that doesn’t work):

main.yml

---

<div class="post-metadata">

**Author:** ![Dimon](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@Dimon](https://forum.ansible.com/u/Dimon)\
**Post date:** [February 22, 2019, 5:08pm UTC](https://forum.ansible.com/t/mangling-include-role-path/29737/2 "2019-02-22T17:08:10Z")

</div>

my current workaround is to stash top-level playbook’s directory and use “include\_tasks” instead of “include\_role”:

main.yml