Closed Wildweasel24 closed 10 years ago
Thank you for reporting this. Which version of ansible are you using? Do you have a somehow special network setup involving proxies?
Ansible v1.7.
No proxies or special network setups, although I do have both VM Workstation and Virtualbox running on the system. Both using default network settings, with no issues.
E43 build was working 3 days ago, I destroyed the working VM, deleted local git repo and files and did a fresh clone to desktop. Then problem above appeared.
Just tried again.. vagrant destroyed VM, did a fresh Vagrant Up and repeatable error as above.
Apologies, closed by mistake.
Workaround solution.
/provisioning/roles/bootstrap/tasks/zsh.yml
Added accept_hostkey = True to end of line 5
git: repo=git://github.com/robbyrussell/oh-my-zsh.git dest=/home/vagrant/.oh-my-zsh update=no accept_hostkey=True
Yeah that works, however I noticed that there still are some other issues I'll fix in the next code push.
TASK: [bootstrap | Clone oh-my-zsh repo] ** failed: [vagrant43] => {"failed": true} msg: github.com has an unknown hostkey. Set accept_hostkey to True or manually add the hostkey prior to running the git module
FATAL: all hosts have already failed -- aborting
PLAY RECAP **** to retry, use: --limit @/home/vagrant/vagrant.retry
vagrant43 : ok=8 changed=4 unreachable=0 failed=1