Using AWX 13.0.0 (Ansible 2.9.10)
The playbook:
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.
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
That verbose output you see, is telling you how ansible-playbook was invoked from the command line. It does not reflect inventory variables.
Thanks again Matt, i’m hitting a wall here, any suggestions?
When running it from the Ansible (command line) it works perfectly, but in AWX it seems to be stuck on using sudo as become method!
I’d consult the IRC channel or mailing list for AWX and seek help there. This mailing list is for ansible proper, so you may not find too much in depth AWX knowledge here.