Support for Berkshelf 5.x

berkshelf / vagrant-berkshelf

A Vagrant plugin to add Berkshelf integration to the Chef provisioners

Other

378 stars 100 forks source link

Support for Berkshelf 5.x #305

Closed cj-saulius-tvarijonas closed 8 years ago

cj-saulius-tvarijonas commented 8 years ago

Vagrant Berkshelf requires ~> 4.0, but the current version is 5.1.0.

jameyg commented 8 years ago

Broken on os x with latest xcode, vagrant, berkshelf and vagrant-berkshelf:

microweb10 commented 8 years ago

I am having the same issue on Ubuntu 14.04 after upgrading chefDK and vagrant to the latest. Previously same Vagrant file was working fine

$ chef -v Chef Development Kit Version: 0.18.26 chef-client version: 12.14.89 delivery version: master (d86679335580be3de22996ef294b20d525889d8d) berks version: 5.1.0 kitchen version: 1.13.0

$ vagrant -v Vagrant 1.8.5

$ vagrant plugin update Updating installed plugins... All plugins are up to date.

$ vagrant up default Bringing machine 'default' up with 'virtualbox' provider... The Berkshelf version at "/usr/bin/berks" is invalid. Vagrant Berkshelf requires ~> 4.0, but the current version is 5.1.0.

Please download and install the latest version of the ChefDK from:

https://downloads.chef.io/chef-dk

and follow the installation instructions. Do not forget to add the ChefDK to your PATH.

Any workaround?

astlock commented 8 years ago

The same problem! Any idea?

microweb10 commented 8 years ago

This worked for me.

Edit this file ~/.vagrant.d/gems/gems/vagrant-berkshelf-5.0.0/lib/vagrant-berkshelf/action/check.rb

where you see: BERKS_REQUIREMENT = "~> 4.0" change it to: BERKS_REQUIREMENT = ">= 4.0"

davidcpell commented 8 years ago

same problem here.

OSX 10.11.6 ChefDK 0.18.26 vagrant-bekshelf 5.0

@microweb10's solution seems to have worked for me

CharlesTBetz commented 8 years ago

seems to have fixed for me as well

Ubuntu 16.04 ChefDK 0.18.26 vagrant-berkshelf 5.0

ericgoedtel commented 8 years ago

That isn't really a good solution, in my opinion. Isn't .vagrant.d in .gitignore? This is not exactly a portable change. It works fine on an individual change but it doesn't really work for a Vagrant implementation that is shared amongst a distributed team. Anyone have any feedback on a permanent fix?

microweb10 commented 8 years ago

After the approval of this PR, you should be able to upgrade vagrant-berkshelf plugin and the issue should be gone ;)

https://github.com/berkshelf/vagrant-berkshelf/pull/306

Dreeg commented 8 years ago

The solution of @microweb10 worked for me 👍

ericgoedtel commented 8 years ago

For some reason, the formal fix that implements the workaround isn't passing CI. May want to use with caution.

nickma commented 8 years ago

Same issue here on all fresh OSX and Vagrant install. Workaround from @microweb10 works.

thommay commented 8 years ago

Fixed by #307, we'll do a release soon.

thommay commented 7 years ago

This was released in 5.1.1 in December.