search

nsidc / vagrant-vsphere

VMware vSphere provider for Vagrant
Other
608 stars 166 forks source link

vagrant-vsphere install fails on vagrant 2.2.1 #271

Closed ssaanncchheezz closed 5 years ago

ssaanncchheezz commented 5 years ago

After upgrading to vagrant 2.2.1, I am unable to install the vagrant-vsphere plugin. After downgrading to 2.1.5 it seems to be working again.

Error: 

Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

conflicting dependencies i18n (~> 0.6.4) and i18n (= 1.1.1)
  Activated i18n-1.1.1
  which does not match conflicting dependency (~> 0.6.4)

  Conflicting dependency chains:
    i18n (= 1.1.1), 1.1.1 activated

  versus:
    vagrant-vsphere (> 0), 0.5.0 activated, depends on
    i18n (~> 0.6.4)
bjneuhaus commented 5 years ago

got exactly the same - nice to know I am not alone ;) but you can get to 2.2.0 so it's not so far away:

[bjoern@CPC6128 ~]$ vagrant --version
Vagrant 2.2.0
[bjoern@CPC6128 ~]$ vagrant plugin install vagrant-vsphere
Installing the 'vagrant-vsphere' plugin. This can take a few minutes...
Fetching: trollop-2.9.9.gem (100%)
!    The 'trollop' gem has been deprecated and has been replaced by 'optimist'.
!    See: https://rubygems.org/gems/optimist
!    And: https://github.com/ManageIQ/optimist
Fetching: mini_portile2-2.3.0.gem (100%)
Fetching: nokogiri-1.8.5.gem (100%)
Building native extensions.  This could take a while...
Fetching: rbvmomi-1.13.0.gem (100%)
Fetching: vagrant-vsphere-1.13.2.gem (100%)
Installed the plugin 'vagrant-vsphere (1.13.2)'!
mattiasa commented 5 years ago

I got the same. Downgrade of Vagrant to 2.2.0 solved the issue for me as well.

thegreenbear commented 5 years ago

Same here.

ghost commented 5 years ago

Fixed with release v1.13.3