# inconsistant when accessing fact attributes

**URL:** <https://forum.ansible.com/t/inconsistant-when-accessing-fact-attributes/17020>\
**Category:** Ansible Project\
**Created:** [December 11, 2014, 3:54am UTC](https://forum.ansible.com/t/inconsistant-when-accessing-fact-attributes/17020 "2014-12-11T03:54:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Steve\_Kieu](https://avatars.discourse-cdn.com/v4/letter/s/41988e/32.png) [@Steve\_Kieu](https://forum.ansible.com/u/Steve_Kieu)\
**Post date:** [December 11, 2014, 3:54am UTC](https://forum.ansible.com/t/inconsistant-when-accessing-fact-attributes/17020/1 "2014-12-11T03:54:36Z")

</div>

Hi Team,

When I first create a docker container which is centos6 based. Run ansible setup and the fact return for “ansible\_selinux” is a boolean.

After a while not sure what has been done if runs setup again - the value now is a dict.

“ansible\_selinux”: {  
“status”: “disabled”  
},

That makes harder in the condition I use. Should we have the dict at the beginning?

Thanks

---

<div class="post-metadata">

**Author:** ![James\_Cammarata](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@James\_Cammarata](https://forum.ansible.com/u/James_Cammarata)\
**Post date:** [December 11, 2014, 3:35pm UTC](https://forum.ansible.com/t/inconsistant-when-accessing-fact-attributes/17020/2 "2014-12-11T15:35:58Z")

</div>

Hi Steve,

Could you open an issue on github for this? My guess would be that the target OS being detected is different between the runs, and the differing methods used for each OS are returning the inconsistent results. We can definitely look into that.

Thanks!