I am running into an interesting issue, and wondered if anyone has hit the same thing as I have. We have our sudo configs locked down pretty tight, and don't allow users to do execute a shell directly using sudo. So, basically, things like sudo /bin/sh are not permitted. I found a 5 year old stacktrace article with a workaround, and I am not particularly fond of the suggestion, which was to make a copy of /bin/sh as a different filename, then tell ansible to use that via the ansible config. ( https://stackoverflow.com/questions/33529850/ansible-have-sudo-but-no-root)
Has anyone seen this before, and if so, I am curious as to what your workaround was. --john -- 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/CAPAjob91%3DqAwxMYzRi56%2B%2Bwo83JYB-bijMyc%3D-v8U_y6g3ck8A%40mail.gmail.com.
