Broken with 0.7.2 about vagrant HOT 12 CLOSED

@EugenMayer

Could you tell me for sure what fails? Your comments above are a little confusing. I'm running chefdk 2.4.17 and have had other problems trying to use chefdk 2.5. Using 2.4.17, everything I can think to try from above has worked.

"chef exec berks vendor cookbooks" works for me using chefdk 2.5.3 but I had to be careful with the install of 2.5.3.
Regards,
Mark

from vagrant.

All i can say you, with the current chefDK you cannot use berks to get vargant 0.7.2, but it works with 0.7.1 - i cannot provide more then above, sorry (i do not have anything more)

Obviously changes for 0.7.2 seems have cause that

from vagrant.

This looks like a berkshelf problem, not one with the cookbook itself.

from vagrant.

You mean without any berks update done, and 0.7.1 working with the current "updated" berks - and every single other cookbook working with the current berk ( about 60 ) you really consider this being a bug in berks? I mean, at least one other would fail too, wouldnt it?

Without understanding the error, the implementation of vagrant or berks, this is extremely unlikely, isnt it?

from vagrant.

Hi @EugenMayer
I did install chefdk 2.5.3 and test the command you indicated had a problem. I vendored the 0.7.2 version without a problem. I needed two attempts to get 2.5.3 installed without leftovers from a previous chefdk install, I had to wipe out ~/.chefdk. But in that situation it failed for every cookbook when it failed for 0.7.2. I have some fixes coming up. We'll see what happens in the next version.

Mark

from vagrant.

@MarkGibbons are you directing into an issue with the upgrade of chefdk ( so i have an unclean upgrade state ) and thats the root of the cause or could you reproduce that actual issue with the vagrant cookbook? thanks for looking at this one

from vagrant.

The root cause is almost definitely related to the ChefDK install or state of ~/.chefdk, that's what I was hinting at earlier as it would be extremely unlikely for the cookbook or it's constituent code to cause the error seen above.

And I've found where this is - it's a RubyGems issue: berkshelf/berkshelf#1744

from vagrant.

Do you want to fix the root of the cause or want me to just flush ~/.chefdk / clean state install chefdk and ignore the issue.

I could do both, but if you would like to fix it, i keep the current state for reproduction / analysis to help you guys find the cause.

from vagrant.

There is nothing to fix in the cookbook for this problem - the root cause is a RubyGems bug upstream rubygems/rubygems#2213. The fix is either Berks can try to catch this itself or RubyGems will get an updated.

from vagrant.

@EugenMayer

Berkshelf has a discussion of the problem and possibly a link to a fix. I'm going to close this issue as its cause is not related to the vagrant cookbook. I've seen this a handful of times now on a variety of other cookbooks. I hope this link might help you.

berkshelf/berkshelf#1744

Regards,
Mark

from vagrant.

thank you mark

from vagrant.

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

from vagrant.