Hi all
I had few sudo issues in the past, and those got solved. Now after updating
to latest release (1.5.3) the problem has resurfaced again.
My master box has an ansible user. Which connects through ssh certs and has
sudo rights to root on each of the remote boxes.
I've got 62 boxes that are failing if I sudo to them with ansible. Those 62
are a mixture to rhel/centos 5.?/6.? 32/64. Nothing in common.
Examples below are shown using a single box.
So if I do not use sudo, it works:
$ ansible commando -om ping
commando | success >> {"changed": false, "ping": "pong"}
Now with sudo:
$ ansible commando -sKom ping
sudo password:
commando | FAILED => ssh connection closed waiting for sudo or su password
prompt
and yet:
$ ssh commando
Last login: Thu Mar 20 12:02:12 2014 from ansible_master.passmark.net
[ansible@commando ~]$ sudo su -
[sudo] password for ansible:
[root@commando ~]# id
uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk
),10(wheel)
I actually updated to dev as I was told that my previous sudo issues had
been solved in the dev branch. Unfortunately no difference. (It got rid of
the nagging "previous host file not found" message thou)
Any help to try to clear this issue for once and for all would be very
welcome indeed.
Thanks
--
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/74e9609c-e50e-46ea-8d34-ae331d47f52e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
