That verbose output you see, is telling you how `ansible-playbook` was
invoked from the command line.  It does not reflect inventory variables.

On Thu, Aug 6, 2020 at 10:59 AM Wafi sh <[email protected]> wrote:

> Thank Matt,
>
> I have tried to add "become_method: winrm" to the group variable but the
> template still shows become_method: sudo when running it.
> Here is the inventory group variables i'm using for the group "
> win_test_nce" in inventory "win-test":
> ansible_connection: winrm
> ansible_winrm_server_cert_validation: ignore
> become_method: runas
>
>
> The playbook output is with verbosity:
> PLAYBOOK: dns-fix-win.yml
> ******************************************************
> Positional arguments: dns-fix-win.yml
> verbosity: 4
> ask_pass: True
> remote_user: ccitops.admin
> connection: smart
> timeout: 10
> become: True
> become_method: sudo
> tags: ('all',)
> inventory: ('/tmp/awx_74_qrt3a82d/tmp3pzi6c98',)
> subset: win_test_nce
> extra_vars: ('@/tmp/awx_74_qrt3a82d/env/extravars',)
> ask_vault_pass: True
> forks: 5
> 1 plays in dns-fix-win.yml
>
>
>
> On Tuesday, August 4, 2020 at 4:30:48 PM UTC-4, Matt Martz wrote:
>>
>> This indicates you are running the playbook with become, or the inventory
>> specifies the hosts use become.  However, you have not configured the
>> become_method for those Windows hosts to use `runas` instead of the default
>> `sudo`.
>>
>> On Tue, Aug 4, 2020 at 2:57 PM Wafi sh <[email protected]> wrote:
>>
>>> Using AWX 13.0.0 (Ansible 2.9.10)
>>>
>>> The playbook:
>>>
>>> -------------------------------------
>>> - hosts: all
>>>   name: DNS Fix Windows
>>>   gather_facts: no
>>>
>>>   tasks:
>>>     - name: Check datacenter
>>>       win_shell: |
>>>           CODE-BLOCK
>>>       register: datacenter
>>>
>>> -----------------------------------
>>>
>>> AWX error:
>>>
>>> {
>>>     "msg": "The powershell shell family is incompatible with the sudo
>>> become plugin",
>>>     "_ansible_no_log": false
>>> }
>>>
>>>
>>>
>>> This is working on Ansible 2.9.0 without AWX.
>>>
>>> --
>>> 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 view this discussion on the web visit
>>> https://groups.google.com/d/msgid/ansible-project/f7ec15e4-7785-456e-bebe-fa4b3e0388a9o%40googlegroups.com
>>> <https://groups.google.com/d/msgid/ansible-project/f7ec15e4-7785-456e-bebe-fa4b3e0388a9o%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>
>>
>> --
>> Matt Martz
>> @sivel
>> sivel.net
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/c52a88ab-5d3f-41c5-b363-22d87ada1bbdo%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/c52a88ab-5d3f-41c5-b363-22d87ada1bbdo%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Matt Martz
@sivel
sivel.net

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAD8N0v_hoMuq2H-4vQj%2BCb%2BQTpTdiKKROi9bWO5-OSoe8_qvTw%40mail.gmail.com.

Reply via email to