Sometimes, manually restarting the networking service is needed for successful provisioning
Ansible provisioning sometimes fails, e.g.
TASK [attacker : Install medusa] ***********************************************
task path: /vagrant/provisioning/roles/attacker/tasks/main.yml:9
<attacker> ESTABLISH LOCAL CONNECTION FOR USER: vagrant
<attacker> EXEC /bin/sh -c 'echo ~vagrant && sleep 0'
<attacker> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo /home/vagrant/.ansible/tmp/ansible-tmp-1603786052.35188-228959837234390 `" && echo ansible-tmp-1603786052.35188-228959837234390="` echo /home/vagrant/.ansible/tmp/ansible-tmp-1603786052.35188-228959837234390 `" ) && sleep 0'
Using module file /usr/lib/python3/dist-packages/ansible/modules/packaging/os/apt.py
<attacker> PUT /home/vagrant/.ansible/tmp/ansible-local-1596gxrtwne2/tmpwrq4ex96 TO /home/vagrant/.ansible/tmp/ansible-tmp-1603786052.35188-228959837234390/AnsiballZ_apt.py
<attacker> EXEC /bin/sh -c 'chmod u+x /home/vagrant/.ansible/tmp/ansible-tmp-1603786052.35188-228959837234390/ /home/vagrant/.ansible/tmp/ansible-tmp-1603786052.35188-228959837234390/AnsiballZ_apt.py && sleep 0'
<attacker> EXEC /bin/sh -c 'sudo -H -S -n -u root /bin/sh -c '"'"'echo BECOME-SUCCESS-wznjzabdgtujegasnscogvxdtmogdiuy ; /usr/bin/python3 /home/vagrant/.ansible/tmp/ansible-tmp-1603786052.35188-228959837234390/AnsiballZ_apt.py'"'"' && sleep 0'
<attacker> EXEC /bin/sh -c 'rm -f -r /home/vagrant/.ansible/tmp/ansible-tmp-1603786052.35188-228959837234390/ > /dev/null 2>&1 && sleep 0'
fatal: [attacker]: FAILED! => {
"changed": false,
"invocation": {
"module_args": {
"allow_unauthenticated": false,
"autoclean": false,
"autoremove": false,
"cache_valid_time": 0,
"deb": null,
"default_release": null,
"dpkg_options": "force-confdef,force-confold",
"force": false,
"force_apt_get": false,
"install_recommends": null,
"name": "medusa",
"only_upgrade": false,
"package": [
"medusa"
],
"policy_rc_d": null,
"purge": false,
"state": "present",
"update_cache": true,
"upgrade": null
}
},
"msg": "Failed to update apt cache: "
}
You need to log in as root, run # service networking reload
, and then vagrant provision
again.
Tested with
- Windows 10 host system
- Vagrant 2.2.7
- munikypo/kali box version 0.0.1