I got the same error as Gergo. After resuming my work VM (I work inside an Ubuntu VM on a Windows machine). Literally nothing happened between the last "vagrant provision" I did a few days ago and the one I tried after resuming the paused Ubundu VM.
The file vagrant is looking for exists:gilles@ubuntu:~/Documents/Mediawiki/vagrant$ vagrant provision ==> default: Running provisioner: lsb_check... ==> default: Running provisioner: shell... default: Running: /tmp/vagrant-shell20170109-41388-12wl00c.sh ==> default: Running provisioner: puppet... ==> default: Running Puppet with site.pp... ==> default: Error: Could not run: Could not find file /vagrant/puppet/manifests/site.pp The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong. gilles@ubuntu:~/Documents/Mediawiki/vagrant$ ls -al puppet/manifests/site.pp -rw-rw-r-- 1 gilles gilles 1739 Sep 24 18:11 puppet/manifests/site.pp
I've found the cause, it's when you enable a role that reloads the VM. You don't even need to actually provision the role, in fact, just marking the VM for needing to restart on provisioning is enough. Steps to reproduce:
- vagrant up
- vagrant roles enable varnish
- vagrant roles reset
- vagrant provision You'll get a first error, apt-related:The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed! apt-get update Stdout from the command: Stderr from the command: E: Archives directory /vagrant/cache/apt/partial is missing. - Acquire (2: No such file or directory)
Then if you attempt to provision again, you get the missing site.pp error.