# Setting dynamic 'become' doesn't work #11381

**URL:** <https://forum.ansible.com/t/setting-dynamic-become-doesnt-work-11381/18812>\
**Category:** Ansible Project\
**Created:** [July 21, 2015, 7:09am UTC](https://forum.ansible.com/t/setting-dynamic-become-doesnt-work-11381/18812 "2015-07-21T07:09:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Albert\_Mikaelyan](https://avatars.discourse-cdn.com/v4/letter/a/7c8e57/32.png) [@Albert\_Mikaelyan](https://forum.ansible.com/u/Albert_Mikaelyan)\
**Post date:** [July 21, 2015, 7:09am UTC](https://forum.ansible.com/t/setting-dynamic-become-doesnt-work-11381/18812/1 "2015-07-21T07:09:38Z")

</div>

Closed issue 11381 still **not** fixed:  
[https://github.com/ansible/ansible/issues/11381](https://github.com/ansible/ansible/issues/11381)

The test done by [jimi-c](https://github.com/jimi-c) is not related (he was setting ‘become\_user’, not ‘become’).

Here is my test, which shows the problem (using latest devel):

$ cat 11381.yml

`

---

<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:** [July 21, 2015, 12:31pm UTC](https://forum.ansible.com/t/setting-dynamic-become-doesnt-work-11381/18812/2 "2015-07-21T12:31:10Z")

</div>

Hi Albert, the original issue was about an error regarding that value being set to yes and it failing to work. I did a follow-up test with that and it worked, however there was no mention of the above in the issue, so I’ll re-open the issue.

---

<div class="post-metadata">

**Author:** ![Albert\_Mikaelyan](https://avatars.discourse-cdn.com/v4/letter/a/7c8e57/32.png) [@Albert\_Mikaelyan](https://forum.ansible.com/u/Albert_Mikaelyan)\
**Post date:** [July 21, 2015, 12:43pm UTC](https://forum.ansible.com/t/setting-dynamic-become-doesnt-work-11381/18812/3 "2015-07-21T12:43:58Z")

</div>

You are right, 1.9.1 was throwing an error, but devel was showing the behaviour of always setting it to ‘true’, as I mentioned on my comment to Brian Coca (and showed here as well)
