Thanks for the information Jordan. I'll give that a try soon, i've worked around the issue by running the playbook as the user in question but that's not the best solution in my mind.
On Monday, 29 October 2018 21:14:56 UTC, Jordan Borean wrote: > > Thanks for that, the user seems to have the correct rights and it does > confirm the win_whoami was run with become. The error you are getting is > probably due to the become process outputting plaintext values where in a > normal case it would base64 encode the output to deal with unicode issues. > > I'm pretty sure I've fixed that in 2.8/devel so it would be great if you > could try it out there. If you can follow > https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#running-from-source > > and run Ansible straight from source on the devel branch that would be > great. You can also set an environment variable on the Windows host > 'ANSIBLE_EXEC_DEBUG' to the path to a local file, if that is set then the > exec wrapper will output debug logs to that file and give you a better > picture as to what's going on. > > If you still get an error it would be great if you could share the debug > logs from the wrapper, it shouldn't contain any sensitive information but > make sure you double check before posting it just in case. > > 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/d09445a4-9f12-47a4-b09d-6a5770263b72%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
