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)

On Tuesday, July 21, 2015 at 3:31:15 PM UTC+3, James Cammarata wrote:
>
> 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.
>
> James Cammarata
> Director, Ansible Core Engineering
> github: jimi-c
>
> On Tue, Jul 21, 2015 at 3:09 AM, Albert Mikaelyan <[email protected] 
> <javascript:>> wrote:
>
>> Closed issue 11381 still *not* fixed:
>> 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
>>  --- 
>> - hosts: antest 
>>  gather_facts: no 
>>  tasks: 
>>  - command: whoami 
>>  become: "{{ app_become }}" 
>>  become_user: my_user 
>>
>> $ ansible-playbook 11381.yml -vv -e app_become=no
>>
>>  Using /home/albert/ansible/ansible.cfg as config file 
>>> 1 plays in 11381.yml 
>>>
>>> PLAY 
>>> ****************************************************************************
>>>  
>>>
>>>
>>> TASK [command] 
>>> ****************************************************************** 
>>> changed: [antest] => {"changed": true, "cmd": ["whoami"], "delta": 
>>> "0:00:01.003433", "end": "2015-07-21 09:50:32.955368", "rc": 0, "start": 
>>> "2015-07-21 09:50:31.95193
>>> 5", "stderr": "", "stdout": "my_user", "stdout_lines": ["my_user"], 
>>> "warnings": []} 
>>>                                                                             
>>>       
>>>  
>>>
>>> PLAY RECAP 
>>> ********************************************************************** 
>>> antest                     : ok=1    changed=1    unreachable=0 
>>>    failed=0
>>>
>>
>> *It still sets* 
>> *'become: yes'*However there's this workaround:
>>
>>  $ cat 11381-2.yml
>> --- 
>> - hosts: antest 
>>  gather_facts: no 
>>  tasks: 
>>  - command: whoami 
>>  become: "{{ app_become | default('False') | bool }}" 
>>  become_user: my_user 
>>
>>
>> $ ansible-playbook 11381.yml -vv -e app_become=false 
>>
>>  Using /home/albert/ansible/ansible.cfg as config file 
>>> 1 plays in 11381.yml 
>>>
>>> PLAY 
>>> ****************************************************************************
>>>  
>>>
>>>
>>> TASK [command] 
>>> ****************************************************************** 
>>> changed: [antest] => {"changed": true, "cmd": ["whoami"], "delta": 
>>> "0:00:00.002272", "end": "2015-07-21 09:55:17.910846", "rc": 0, "start": 
>>> "2015-07-21 09:55:17.90857
>>> 4", "stderr": "", "stdout": "root", "stdout_lines": ["root"], 
>>> "warnings": []} 
>>>                                                                             
>>>             
>>>  
>>>
>>> PLAY RECAP 
>>> ********************************************************************** 
>>> antest                     : ok=1    changed=1    unreachable=0 
>>>    failed=0
>>>
>>
>>
>>
>>
>>   -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Ansible Project" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ansible-project/b7b37211-6cb9-4101-8f88-41fe2654fdbe%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/ansible-project/b7b37211-6cb9-4101-8f88-41fe2654fdbe%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/b79bd67e-c77f-4f99-af0e-6b63513243c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to