These are the issues I've raised for anyone else having this problem:

https://github.com/mitchellh/vagrant-aws/issues/385
https://github.com/berkshelf/vagrant-berkshelf/issues/281

On 7 May 2015 at 10:26, Yoshi Spendiff <[email protected]> wrote:

> Thanks, Alvaro.
>
> I raised a ticket. There doesn't look to be any movement on the
> vagrant-was plug-in though so I'm not expecting anything.
>
> The difference between the AWS provider and say, Virtualbox, is that the
> vagrant-chef directory is mounted when using Virtualbox and is thus updates
> when vagrant-berkshelf updates the local shelf. On AWS this directory is
> rsynced on initial up but not on provision.
>
> I'll raise a ticket for vagrant-berkshelf as well to see if there's a
> solution from that end.
>
>
> On 5 May 2015 at 14:13, Alvaro Miranda Aguilera <[email protected]> wrote:
>
>> On Wed, May 6, 2015 at 4:19 AM, Yoshi Spendiff <[email protected]>
>> wrote:
>> > ~/.berkshelf/vagrant-berkshelf/shelves/berkshelf<some
>> identifier>/cookbook
>> > and I can see my updates in there. When provisioning is finished I can
>> also
>> > see the recipe changes applied to /vagrant/recipes.
>> >
>> > None of this is useful though as the cookbooks are run from
>> > /tmp/vagrant-chef/<hash>/cookbooks
>>
>> Hello,
>>
>> I am not a chef user, so if I am saying something crazy, please forgive
>> me..
>>
>> If on initial provision works, and then on new provision/reload
>> doesn't, I think you can open an issue on github.
>>
>> Alvaro.
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Vagrant" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/vagrant-up/_xe5dy9S5Eo/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> [email protected].
>> 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.

Reply via email to