Try using Ansible become to workaround this problem. It isn’t a guarantee but 
it acts like the process was executed on an interactive logon. You could have 
trouble if the command is expecting user input. This can’t be done on Ansible.

-- 
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/e8bed54c-2729-4c64-8bd8-36fce1ae3a85%40googlegroups.com.

Reply via email to