Makes no difference. Torben's workaround, though, does. On Tuesday, May 12, 2015 at 5:11:47 PM UTC-5, Alvaro Miranda Aguilera wrote: > > Can you test > > vagrant reload --provision > > > On Wed, May 13, 2015 at 7:52 AM, Jeff Sussna <[email protected] > <javascript:>> wrote: > > Have a Vagrantfile with a chef-solo provisioner and a few cookbooks. > > 'vagrant up' and 'vagrant provision' work fine. However, after 'vagrant > > reload' the cookbooks appear to have been deleted from the guest. On a > > Centos guest, /tmp/vagrant-chef/.../cookbooks directory on the guest is > > empty. On an Ubuntu guest, /tmp/vagrant-chef is empty. In either case > > provisioning fails. Have never seen this behavior before. Running > Vagrant > > 1.72/VirtualBox 4.3/OSX Yosemite. > > > > -- > > 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] <javascript:>. > > For more options, visit https://groups.google.com/d/optout. >
-- 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.
