![]() SSH: EXEC sshpass -d14 ssh -C -vvv -o ServerAliveInterval=50 -o ESTABLISH SSH CONNECTION FOR USER: vagrant Results now, after recreating both vms: # ansible-playbook -i vms -k -u vagrant vms.yml -vvvv In any case, the problem has not gone away. Not sure if it's got something to do with the vm I'm doing deployment from being rebooted in the meantime, or the receiving machine being destroyed and uped completely since then. This was in the evening, and I was very tired, and this error didn't recur the following morning. ![]() But when I run my ansible playbook, ansible fails.Īt first I got the message " ssh: connect to host 10.1.2.100 port 22: No route to host" when running ansible with -vvvv I can ssh into the other machines without trouble. Unfortunately my host is a windows machine, so I thought I could solve the issue by putting all the vms into a vpn and then provision them from another machine in the same vpn. I wrote a script to run up several vms using vagrant, which I have to then provision with ansible.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |