solved!
At the end it was something simple (isn't it always...)
On the client machines, /etc/sudoers had this fateful line:
Defaultsrequiretty
That has been commented out. And no issues.
But I feel ambivalent about the security side of things. Is there no way
for ansible to log with a
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
Makimoto,
Have you enabled 'pipelining = True' in your ansible.cfg file?
If so, this is potentially the cause. Regardless, it would be nice to see the
output of ansible - as that would help identify if pipelining is being used
or not, or any other potential issues.
--
Matt Martz
Hi
Pipelining is most definitely on. The speed advantage is great. I tried
disabling it and see, but the end result is the same.
with pipelining on:
$ ansible commando -sKom ping -
sudo password:
commando ESTABLISH CONNECTION
For the record I do have this on ansible.cfg:
remote_tmp = /tmp
On Thursday, 20 March 2014 14:34:06 UTC, Makimoto Marakatti wrote:
Hi
Pipelining is most definitely on. The speed advantage is great. I tried
disabling it and see, but the end result is the same.
with pipelining on:
$
By the way, I did forget to mention that I tried to give a passwordless
sudo access to the 'ansible' user.
And did not work. Got the same output.
Which leads me to think that sudo does not get called properly.
Just speculating thou
On Thursday, 20 March 2014 14:35:19 UTC, Makimoto Marakatti
What was the last official release that worked for you? Also, are there any
other ansible.cfg settings you've changed from their defaults?
On Thu, Mar 20, 2014 at 10:11 AM, Makimoto Marakatti makim...@gmail.comwrote:
By the way, I did forget to mention that I tried to give a passwordless
sudo
Hi
Last working one was 1.5.1.
And yes few changes to the cfg. Here the comments stripped version:
[defaults]
hostfile = /ansible/etc/hosts
library= /usr/share/ansible
remote_tmp = /tmp
pattern= *
forks = 5
poll_interval = 15
sudo_user = root
transport
that's a good point. haven't tried.
Will try tomorrow at work and report back.
thanks!
On Thursday, 20 March 2014 17:58:45 UTC, James Cammarata wrote:
I see you've set you're setting the transport to ssh rather than smart,
when you're using EL 5/6, does the same issue occur if you set the
