Become and Windows was still experimental in Ansible 2.4 but not much
changed between 2.4 to 2.5+ apart from new features being added. Are you
able to try and run your task with the following vars set to rule out an
incorrect password being set;
- module:
vars:
ansible_become: yes
ansible_become_method: runas
ansible_become_user: [email protected]
ansible_become_pass: password
Can you also share the following;
* How are you calling your module with become, are you enabling it from
your playbook or cmdline or have you added '#AnsibleRequires -Become' to
your module
* When you say whoami or win_command work fine, do you mean that become
works with them?
This is a weird one because what you are saying it true, the module should
not affect the become side as it cannot control the become process, except
to tell Ansible that become is required with the '#AnsibleRequires -Become'
flag.
Thanks
Jordan
--
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/8885348d-2913-433a-803f-35e8d741033e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
