devopsgroup-io/vagrant-hostmanager

Incompatible with Vagrant 1.9.7

jk779 opened this issue · 7 comments

jk779 commented

Hi,
I just tried to install this Plugin on the currently newest version of Vagrant, which yields the following error:

Installing the 'vagrant-hostmanager' plugin. This can take a few minutes...
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 winrm-fs (= 1.0.1) and winrm-fs (= 0.3.2)
  Activated winrm-fs-0.3.2
  which does not match conflicting dependency (= 1.0.1)

  Conflicting dependency chains:
    winrm-fs (= 0.3.2), 0.3.2 activated

  versus:
    winrm-fs (= 1.0.1)

  Gems matching winrm-fs (= 1.0.1):
    winrm-fs-1.0.1

After downgrading Vagrant to the officially supported vagrant version (1.9.4), the installation works.

Just wanted to let you know!

mtourtellott commented

Me Too!

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 winrm-fs (= 1.0.1) and winrm-fs (= 0.2.0)
Activated winrm-fs-0.2.0
which does not match conflicting dependency (= 1.0.1)

Conflicting dependency chains:
winrm-fs (= 0.2.0), 0.2.0 activated

versus:
winrm-fs (= 1.0.1)

Gems matching winrm-fs (= 1.0.1):
winrm-fs-1.0.1

jjmiv commented

same from version 2.0. conflict may have occurred before i upgraded though:

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 winrm-fs (= 1.0.1) and winrm-fs (= 0.2.0)
Activated winrm-fs-0.2.0
which does not match conflicting dependency (= 1.0.1)

Conflicting dependency chains:
winrm-fs (= 0.2.0), 0.2.0 activated

versus:
winrm-fs (= 1.0.1)

Gems matching winrm-fs (= 1.0.1):
winrm-fs-1.0.1

mikymartin commented

Me too!
Got error during installation of vagrant-hostsupdater

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 winrm-fs (= 1.0.1) and winrm-fs (= 0.3.2)
Activated winrm-fs-0.3.2
which does not match conflicting dependency (= 1.0.1)

Conflicting dependency chains:
winrm-fs (= 0.3.2), 0.3.2 activated

versus:
winrm-fs (= 1.0.1)

Gems matching winrm-fs (= 1.0.1):
winrm-fs-1.0.1

slastique commented

I've got same errors on fresh Fedora 27 installation, the root cause, in my case, was in vagrant installed during Fedora installation. I removed it and install from rpm from Vagrant site

chuckreynolds commented

Same issue.

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 rest-client (= 2.0.2) and rest-client (= 1.6.9)
  Activated rest-client-1.6.9
  which does not match conflicting dependency (= 2.0.2)

  Conflicting dependency chains:
    rest-client (= 1.6.9), 1.6.9 activated

  versus:
    rest-client (= 2.0.2)

  Gems matching rest-client (= 2.0.2):
    rest-client-2.0.2
  • Vagrant 2.0.1
  • Gem -v 2.6.12
  • Virtual Box: 5.2.6 r120293 (Qt5.6.3)

Running vagrant plugin install vagrant-hostmanager causes the above error.

chuckreynolds commented

after some research I found an ENV var to include that helps bypass a common issue?
VAGRANT_DISABLE_STRICT_DEPENDENCY_ENFORCEMENT=1 vagrant plugin install vagrant-hostmanager
Which seems to install it...

Installing the 'vagrant-hostmanager' plugin. This can take a few minutes...
Fetching: vagrant-share-1.1.9.gem (100%)
Fetching: vagrant-hostmanager-1.8.7.gem (100%)
Installed the plugin 'vagrant-hostmanager (1.8.7)'!

vagrant plugin list shows it's installed:

vagrant-hostmanager (1.8.7)
vagrant-share (1.1.9, system)

But on vagrant up it doesn't seem to actually work.
For now.. back to manually adding new hosts...

bobweston commented

Has anyone found a fix for this?