# Variable precedence in 1.8.4 and 1.6.10

**URL:** <https://forum.ansible.com/t/variable-precedence-in-1-8-4-and-1-6-10/18594>\
**Category:** Ansible Project\
**Created:** [June 24, 2015, 4:25pm UTC](https://forum.ansible.com/t/variable-precedence-in-1-8-4-and-1-6-10/18594 "2015-06-24T16:25:55Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sergey\_Maslyakov](https://avatars.discourse-cdn.com/v4/letter/s/59ef9b/32.png) [@Sergey\_Maslyakov](https://forum.ansible.com/u/Sergey_Maslyakov)\
**Post date:** [June 24, 2015, 4:25pm UTC](https://forum.ansible.com/t/variable-precedence-in-1-8-4-and-1-6-10/18594/1 "2015-06-24T16:25:55Z")

</div>

I observe a strange difference in behavior of Ansible 1.8.4 and 1.6.10.

I have a variable in group\_vars/all and then I override it in the inventory file in the [all:vars] section.

In 1.6.10, it works as expected. The value from [all:vars] in the inventory takes precedence.

In 1.8.6, it is still the value from group\_vars/all that takes precedence.  
If I move the override in the inventory file out of [all:vars] and into an explicit [host\_group:vars] it works fine.

Is there a difference in how [all:vars] is handled in 1.6.10 and 1.8.4?

Regards,  
/Sergey