Something is off after I upgraded to 1.9.2 : configured module search path = None

[blacksensei]

Hello guys,

This is my first post here. After playing around with ansible I decided to introduce it to my team in the office.

After cooking my short tutorial to speed up the adoption of the team, I moved to another project. I just resumed my project today and it looks like it doesn't work any more. I realized I have updated my machine some time last week.
When I check ansible version, It has updated from 1.8.x to 1.9.2.

When I check the version it's shows the following:

ansible --version
ansible 1.9.2
  configured module search path = None

This has been my first time seeing that. Could this be the cause?


I used vagrant and repeated the same command which used to work over and over again and it baffles me.

 ansible all -m ping -i /etc/ansible/myhost -u vagrant -k -s -K -vvvv
SSH password:
SUDO password[defaults to SSH password]:
<192.168.56.103> ESTABLISH CONNECTION FOR USER: vagrant
<192.168.56.103> REMOTE_MODULE ping
<192.168.56.113> ESTABLISH CONNECTION FOR USER: vagrant
<192.168.56.112> ESTABLISH CONNECTION FOR USER: vagrant
<192.168.56.113> REMOTE_MODULE ping
<192.168.56.121> ESTABLISH CONNECTION FOR USER: vagrant
<192.168.56.121> REMOTE_MODULE ping
<192.168.56.112> REMOTE_MODULE ping
<192.168.56.111> ESTABLISH CONNECTION FOR USER: vagrant
<192.168.56.111> REMOTE_MODULE ping
<192.168.56.103> EXEC sshpass -d8 ssh -C -tt -vvv -o ControlMaster=auto -o ControlPersist=60s -o ControlPath="/home/joseph/.ansible/cp/ansible-ssh-%h-%p-%r" -o GSSAPIAuthentication=no -o PubkeyAuthentication=no -o User=vagrant -o ConnectTimeout=10 192.168.56.103 /bin/sh -c 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1435825061.0-191333747067128 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1435825061.0-191333747067128 && echo $HOME/.ansible/tmp/ansible-tmp-1435825061.0-191333747067128'
<192.168.56.121> EXEC sshpass -d13 ssh -C -tt -vvv -o ControlMaster=auto -o ControlPersist=60s -o ControlPath="/home/joseph/.ansible/cp/ansible-ssh-%h-%p-%r" -o GSSAPIAuthentication=no -o PubkeyAuthentication=no -o User=vagrant -o ConnectTimeout=10 192.168.56.121 /bin/sh -c 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1435825061.0-280223897548193 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1435825061.0-280223897548193 && echo $HOME/.ansible/tmp/ansible-tmp-1435825061.0-280223897548193'
<192.168.56.112> EXEC sshpass -d9 ssh -C -tt -vvv -o ControlMaster=auto -o ControlPersist=60s -o ControlPath="/home/joseph/.ansible/cp/ansible-ssh-%h-%p-%r" -o GSSAPIAuthentication=no -o PubkeyAuthentication=no -o User=vagrant -o ConnectTimeout=10 192.168.56.112 /bin/sh -c 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1435825061.0-36810078339601 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1435825061.0-36810078339601 && echo $HOME/.ansible/tmp/ansible-tmp-1435825061.0-36810078339601'
<192.168.56.113> EXEC sshpass -d11 ssh -C -tt -vvv -o ControlMaster=auto -o ControlPersist=60s -o ControlPath="/home/joseph/.ansible/cp/ansible-ssh-%h-%p-%r" -o GSSAPIAuthentication=no -o PubkeyAuthentication=no -o User=vagrant -o ConnectTimeout=10 192.168.56.113 /bin/sh -c 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1435825061.0-14707467925722 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1435825061.0-14707467925722 && echo $HOME/.ansible/tmp/ansible-tmp-1435825061.0-14707467925722'
<192.168.56.111> EXEC sshpass -d12 ssh -C -tt -vvv -o ControlMaster=auto -o ControlPersist=60s -o ControlPath="/home/joseph/.ansible/cp/ansible-ssh-%h-%p-%r" -o GSSAPIAuthentication=no -o PubkeyAuthentication=no -o User=vagrant -o ConnectTimeout=10 192.168.56.111 /bin/sh -c 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1435825061.0-241910772781718 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1435825061.0-241910772781718 && echo $HOME/.ansible/tmp/ansible-tmp-1435825061.0-241910772781718'
192.168.56.113 | FAILED => SSH Error: Host key verification failed.
    while connecting to 192.168.56.113:22
It is sometimes useful to re-run the command using -vvvv, which prints SSH debug output to help diagnose the issue.
192.168.56.112 | FAILED => SSH Error: Host key verification failed.
    while connecting to 192.168.56.112:22
It is sometimes useful to re-run the command using -vvvv, which prints SSH debug output to help diagnose the issue.
<192.168.56.122> ESTABLISH CONNECTION FOR USER: vagrant
<192.168.56.122> REMOTE_MODULE ping
<192.168.56.131> ESTABLISH CONNECTION FOR USER: vagrant
<192.168.56.131> REMOTE_MODULE ping
192.168.56.121 | FAILED => SSH Error: Host key verification failed.
    while connecting to 192.168.56.121:22
It is sometimes useful to re-run the command using -vvvv, which prints SSH debug output to help diagnose the issue.
192.168.56.103 | FAILED => SSH Error: Host key verification failed.
    while connecting to 192.168.56.103:22
It is sometimes useful to re-run the command using -vvvv, which prints SSH debug output to help diagnose the issue.
<192.168.56.132> ESTABLISH CONNECTION FOR USER: vagrant
<192.168.56.132> REMOTE_MODULE ping
192.168.56.111 | FAILED => SSH Error: Host key verification failed.
    while connecting to 192.168.56.111:22
It is sometimes useful to re-run the command using -vvvv, which prints SSH debug output to help diagnose the issue.<192.168.56.122> EXEC sshpass -d11 ssh -C -tt -vvv -o ControlMaster=auto -o ControlPersist=60s -o ControlPath="/home/joseph/.ansible/cp/ansible-ssh-%h-%p-%r" -o GSSAPIAuthentication=no -o PubkeyAuthentication=no -o User=vagrant -o ConnectTimeout=10 192.168.56.122 /bin/sh -c 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1435825061.03-111451223823096 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1435825061.03-111451223823096 && echo $HOME/.ansible/tmp/ansible-tmp-1435825061.03-111451223823096'
<192.168.56.131> EXEC sshpass -d9 ssh -C -tt -vvv -o ControlMaster=auto -o ControlPersist=60s -o ControlPath="/home/joseph/.ansible/cp/ansible-ssh-%h-%p-%r" -o GSSAPIAuthentication=no -o PubkeyAuthentication=no -o User=vagrant -o ConnectTimeout=10 192.168.56.131 /bin/sh -c 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1435825061.04-239226101832594 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1435825061.04-239226101832594 && echo $HOME/.ansible/tmp/ansible-tmp-1435825061.04-239226101832594'

<192.168.56.132> EXEC sshpass -d13 ssh -C -tt -vvv -o ControlMaster=auto -o ControlPersist=60s -o ControlPath="/home/joseph/.ansible/cp/ansible-ssh-%h-%p-%r" -o GSSAPIAuthentication=no -o PubkeyAuthentication=no -o User=vagrant -o ConnectTimeout=10 192.168.56.132 /bin/sh -c 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1435825061.04-123419328640893 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1435825061.04-123419328640893 && echo $HOME/.ansible/tmp/ansible-tmp-1435825061.04-123419328640893'
192.168.56.131 | FAILED => SSH Error: Host key verification failed.
    while connecting to 192.168.56.131:22
It is sometimes useful to re-run the command using -vvvv, which prints SSH debug output to help diagnose the issue.
192.168.56.122 | FAILED => SSH Error: Host key verification failed.
    while connecting to 192.168.56.122:22
It is sometimes useful to re-run the command using -vvvv, which prints SSH debug output to help diagnose the issue.
192.168.56.132 | FAILED => SSH Error: Host key verification failed.
    while connecting to 192.168.56.132:22
It is sometimes useful to re-run the command using -vvvv, which prints SSH debug output to help diagnose the issue.

Is there a configuration I need to fix kindly let me know.

I would also use this opportunity to ask a related question. How do you really boostrap a new node to use ansible pem file? I have a user role which depends on ansible connecting to the target machine the first time using username and password and then creates the ansible user on the target host, put the public key and add ansible user to the sudoers file. Is there a better way of doing this?

Please help me get back on track.

Thanks for reading this.

[Brian Coca]

to your problem with vagrant, i'm going to guess the machines have the
same host key, try setting host_key_checking = False in ansible.cfg

As for the bootstrap, that looks fine when using a shared ansible
user, others just use the root user and others just add individual
users with sudo/su to the machines, it all depends on your policies.



--
Brian Coca