Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vagrant-vsphere install fails on vagrant 2.2.1 #271

Closed
ssaanncchheezz opened this issue Nov 19, 2018 · 4 comments
Closed

vagrant-vsphere install fails on vagrant 2.2.1 #271

ssaanncchheezz opened this issue Nov 19, 2018 · 4 comments

Comments

@ssaanncchheezz
Copy link

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
Copy link

bjneuhaus commented Nov 20, 2018

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
Copy link

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

@thegreenbear
Copy link

Same here.

@ghost
Copy link

ghost commented Dec 19, 2018

Fixed with release v1.13.3

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants