# issue #11996 (include\_vars overrides subsequent role's vars/main.yml)

**URL:** <https://forum.ansible.com/t/issue-11996-include-vars-overrides-subsequent-roles-vars-main-yml/19498>\
**Category:** Ansible Project\
**Created:** [October 13, 2015, 7:22pm UTC](https://forum.ansible.com/t/issue-11996-include-vars-overrides-subsequent-roles-vars-main-yml/19498 "2015-10-13T19:22:33Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dan\_Stillman](https://avatars.discourse-cdn.com/v4/letter/d/ecb155/32.png) [@Dan\_Stillman](https://forum.ansible.com/u/Dan_Stillman)\
**Post date:** [October 13, 2015, 7:22pm UTC](https://forum.ansible.com/t/issue-11996-include-vars-overrides-subsequent-roles-vars-main-yml/19498/1 "2015-10-13T19:22:33Z")

</div>

Can one of the developers please comment on #11996 ([https://github.com/ansible/ansible/issues/11996](https://github.com/ansible/ansible/issues/11996))?

Again, this was acknowledged as a bug by abadger in [1]. It had been fixed in 2.0, but then regressed again (as expected [2]). As I note in the GitHub thread, the current behavior makes role variables completely unreliable and dangerous to use, because if a previous role happens to include a variable with the same name as a role variable from a later role, the role variable is ignored.

[1] [https://github.com/ansible/ansible/issues/11996#issuecomment-133107471](https://github.com/ansible/ansible/issues/11996#issuecomment-133107471)  
[2] [https://groups.google.com/d/msg/ansible-project/4OIuDxRSv0M/RgW8HkuIKQAJ](https://groups.google.com/d/msg/ansible-project/4OIuDxRSv0M/RgW8HkuIKQAJ)