Closed aboltart closed 10 years ago
When I made vagrant reload
then cookbooks directory was mounted and provisioning executed as expected
Output:
vagrant reload
==> default: Attempting graceful shutdown of VM...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 => 2222 (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection timeout. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
default: /vagrant => /Users/foo/work/bar
default: /tmp/vagrant-chef-3/chef-solo-1/cookbooks => /Users/foo/work/bar/cookbooks
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: to force provisioning. Provisioners marked to run always will still run.
Yeah, reloading is the right course of action here. I've seen this a couple of times but I've never seen a reliable repro. If you can reliably reproduce this please send a gist of a vagrant up --debug
.
:+1: for reloading vagrant - it helped me
Vagrant file configuration
cookbooks directory is on the same level as Vagrantfile
content of cookbooks directory:
Vim cokbook was cloned from https://github.com/opscode-cookbooks/vim
I have latest Vagrant
Full stack trace of vagrant provision