Running vagrant reload with --debug shows the following DEBUG messages DEBUG chef_zero: Not sharing /fuse/vendor/cookbooks, exists as /tmp/vagrant-chef/f08a2bbbb718cb37f3752d8907ba1ab2/cookbooks DEBUG chef_zero: Not sharing /fuse/source/cookbooks, exists as /tmp/vagrant-chef/1fef58223c1ebac124dbfcc641481a3c/cookbooks However, the /tmp/vagrant-chef directory doesn't exist in the guest.
It's line 129 in embedded/gems/gems/vagrant-1.7.2/plugins/provisioners/chef/provisioner/chef_solo.rb On Tuesday, February 10, 2015 at 11:24:55 AM UTC-5, Joe George wrote: > > I have a multi node configuration that has been working for awhile. > Something changed recently that has causing the failure. > > Setup: > Vagrant 1.7.2 > OSX Host > VM Fusion 6 (with vagrant-vmware plugin) > Ubuntu 14.04 Guests > Chef 12 > ChefDK 0.4.0 > Provisioner: chef_zero > > My chef cookbooks are installed to separate directories. One for remote > dependencies, the other for my local cookbooks. > > When I first run "up", Vagrant correctly mounts /vagrant, another shared > directory, and the 2 cookbook directories. When I run "reload --provision" > or "up --provision" after halting the VM, the first two shared directories > are mounted, but the cookbook ones are not. This was working until last > week. > > Cookbooks line in my Vagrantfile: > chef.cookbooks_path = ["/fuse/vendor/cookbooks", "/fuse/source/cookbooks"] > > Any suggestions on what this might be or how to troubleshot this? > > Thanks > Joe > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
