invalid output was: [sudo via ansible, key=xfucmmnngaakrzojuosuatbjpbtjsqvc] password:

Archives Ansible Project
1

Hi, hit a wall with a bug and verbose output isn’t helping


GATHERING FACTS ***************************************************************
<127.0.0.1> REMOTE_MODULE setup
<m7b> ESTABLISH CONNECTION FOR USER: vagrant
<m7b> REMOTE_MODULE setup
<127.0.0.1> EXEC ['/bin/sh', '-c', 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1402074540.16-189669884551029 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1402074540.16-189669884551029 && echo $HOME/.ansible/tmp/ansible-tmp-1402074540.16-189669884551029']
<m7b> EXEC ['sshpass', '-d10', 'ssh', '-C', '-tt', '-vvv', '-o', 'ControlMaster=auto', '-o', 'ControlPersist=60s', '-o', 'ControlPath=/Users/Richard/.ansible/cp/ansible-ssh-%h-%p-%r', '-o', 'StrictHostKeyChecking=no', '-o', 'GSSAPIAuthentication=no', '-o', 'PubkeyAuthentication=no', '-o', 'User=vagrant', '-o', 'ConnectTimeout=10', 'm7b', "/bin/sh -c 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1402074540.16-275366681857235 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1402074540.16-275366681857235 && echo $HOME/.ansible/tmp/ansible-tmp-1402074540.16-275366681857235'"]
<127.0.0.1> PUT /var/folders/65/h42y17593yj3rwt2qx_wwvj80000gn/T/tmpZjtRFH TO /Users/Richard/.ansible/tmp/ansible-tmp-1402074540.16-189669884551029/setup
<127.0.0.1> EXEC /bin/sh -c 'sudo -k && sudo -H -S -p "[sudo via ansible, key=xfucmmnngaakrzojuosuatbjpbtjsqvc] password: " -u root /bin/sh -c '"'"'echo SUDO-SUCCESS-xfucmmnngaakrzojuosuatbjpbtjsqvc; /usr/bin/python /Users/Richard/.ansible/tmp/ansible-tmp-1402074540.16-189669884551029/setup; rm -rf /Users/Richard/.ansible/tmp/ansible-tmp-1402074540.16-189669884551029/ >/dev/null 2>&1'"'"''
<m7b> PUT /var/folders/65/h42y17593yj3rwt2qx_wwvj80000gn/T/tmpNrRGvN TO /home/vagrant/.ansible/tmp/ansible-tmp-1402074540.16-275366681857235/setup
failed: [127.0.0.1] => {"failed": true, "parsed": false}
invalid output was: [sudo via ansible, key=xfucmmnngaakrzojuosuatbjpbtjsqvc] password:

More output available here below, any help appreciated.

https://gist.github.com/aggress/a09d875ff961fbfe4423

2

From the output, it looks like it tried to ssh to localhost, but failed. This may be an issue with sshpass, or with sudo/ssh credentials on the system, if you can share any other details about your setup.

3

Thanks James

Ansible’s running locally and I’m hitting a single Vagrant instance using this play

https://github.com/aggress/ansible-mapr/blob/master/hue.yml

I have to split things up because I’m hitting a single node, doing the Hue role then dynamically creating a new host group running an activity on those then a fine task on the original single node. At some point it does look like it’s trying to ssh to localhost but I can’t see why it would do that as in this test it’s only hitting a single node labelled m7b which resolves to 192.168.33.11

4

So, I’ve double checked things, I can’t see any reason why the first play completes successfully and hits node m7b as defined in vagrant_hosts but the second play hits 127.0.0.1 and m7b. It should be a repeat of the first play.