Vagrant: Vagrant 1.7.0 - Bundler error

[maspwr]

I just upgraded to Vagrant 1.7.0 and got the following error.

% vagrant status
Bundler, the underlying system used to manage Vagrant plugins,
is reporting that a plugin or its dependency can't be found.
This is usually caused by manual tampering with the 'plugins.json'
file in the Vagrant home directory. To fix this error, please
remove that file and reinstall all your plugins using `vagrant
plugin install`.
/opt/vagrant/embedded/gems/gems/bundler-1.7.8/lib/bundler/resolver.rb:357:in `resolve': Could not find gem 'vagrant-login (>= 0) ruby' in the gems available on this machine. (Bundler::GemNotFound)
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.8/lib/bundler/resolver.rb:164:in `start'
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.8/lib/bundler/resolver.rb:129:in `resolve'
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.8/lib/bundler/definition.rb:193:in `resolve'
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.8/lib/bundler/definition.rb:132:in `specs'
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.8/lib/bundler/definition.rb:177:in `specs_for'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant.rb:76:in `<top (required)>'
    from /opt/vagrant/embedded/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:118:in `require'
    from /opt/vagrant/embedded/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:118:in `rescue in require'
    from /opt/vagrant/embedded/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:124:in `require'
    from /opt/vagrant/bin/../embedded/gems/gems/vagrant-1.7.0/bin/vagrant:105:in `<main>'

The contents of plugins.json:

% cat ~/.vagrant.d/plugins.json
{"installed":{"vagrant-vmware-fusion":{"ruby_version":"2.0.0","vagrant_version":"1.6.5","gem_version":"","require":"","sources":[]}},"version":"1"}%

[mitchellh]

This is being fixed right now. Sorry about this. New installers will be up in ~30 minutes.

[maspwr]

No worries. Thanks for the quick fix!

[mitchellh]

This is now fixed. Please redownload the installer.

[jravetch]

I installed the updated package, but now I see this:

Vagrant experienced a version conflict with some installed plugins!
This usually happens if you recently upgraded Vagrant. As part of the
upgrade process, some existing plugins are no longer compatible with
this version of Vagrant. The recommended way to fix this is to remove
your existing plugins and reinstall them one-by-one. To remove all
plugins:

rm -r ~/.vagrant.d/plugins.json ~/.vagrant.d/gems

Note if you have an alternate VAGRANT_HOME environmental variable
set, the folders above will be in that directory rather than your
user's home directory.

The error message is shown below:

Bundler could not find compatible versions for gem "rest-client":
In Gemfile:
vagrant (= 1.7.0) ruby depends on
rest-client (~> 1.7) ruby

vagrant-share (>= 0) ruby depends on
  rest-client (1.6.8)

[mitchellh]

Yeah, another set is uploading. Sorry :( -.-

[ptt-homme]

Hi,

Still not working on mac OSX 10.9.5 with a 10 min downloaded version, any ideas please?

[sethvargo]

@ptt-homme the new build is still uploading.

[ptt-homme]

Ok, thanks. I will wait then :)

[mitchellh]

They're up and out!

[maspwr]

Great! Works for me!

[ptt-homme]

Me either, but there are some nasty errors while vagrant up:

/opt/vagrant/embedded/gems/gems/vagrant-1.7.0/plugins/hosts/bsd/cap/nfs.rb:140: warning: character class has '-' without escape: /^# VA│GRANT-BEGIN:( 502)? ([\.\/A-Za-z0-9-_]+?)$/

But the process went at it end, any ideas?

Thanks.

[dcorking]

Have you pushed the fix to the RPM ? I get the same Bundler error as jravetch on Fedora 20 with installer I downloaded 3.5 hours ago. https://gist.github.com/dcorking/44a514b2e0ad828fd595

[wballard]

I'm getting this error right now with Vagrant 1.7.2. Stuck dead.

[welly]

I'm getting similar ruby gem errors with Vagrant 1.7.2. It seems to be working but every time I run a vagrant command, screen full of errors:

/opt/vagrant/embedded/gems/gems/bundler-1.7.11/lib/bundler/spec_set.rb:92:in `block in materialize': Could not find net-ssh-2.9.2 in any of the sources (Bundler::GemNotFound)
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.11/lib/bundler/spec_set.rb:85:in `map!'
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.11/lib/bundler/spec_set.rb:85:in `materialize'
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.11/lib/bundler/definition.rb:132:in `specs'
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.11/lib/bundler/definition.rb:177:in `specs_for'
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.11/lib/bundler/definition.rb:166:in `requested_specs'
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.11/lib/bundler/environment.rb:18:in `requested_specs'
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.11/lib/bundler/runtime.rb:13:in `setup'
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.11/lib/bundler.rb:122:in `setup'
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.11/lib/bundler/setup.rb:17:in `<top (required)>'
    from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'

I'm not sure if it's anything to do with rvm? It appears to be trying to using the system ruby libraries instead.

[reinh]

Also still getting this with 1.7.2

❯ vagrant plugin install vagrant-login
Bundler, the underlying system used to manage Vagrant plugins,
is reporting that a plugin or its dependency can't be found.
This is usually caused by manual tampering with the 'plugins.json'
file in the Vagrant home directory. To fix this error, please
remove that file and reinstall all your plugins using `vagrant
plugin install`.
/opt/vagrant/embedded/gems/gems/bundler-1.7.11/lib/bundler/resolver.rb:368:in `resolve': Could not find gem 'vagrant-login (>= 0) ruby' in the gems available on this machine. (Bundler::GemNotFound)
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.11/lib/bundler/resolver.rb:166:in `start'
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.11/lib/bundler/resolver.rb:129:in `resolve'
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.11/lib/bundler/definition.rb:193:in `resolve'
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.11/lib/bundler/definition.rb:132:in `specs'
    from /opt/vagrant/embedded/gems/gems/bundler-1.7.11/lib/bundler/definition.rb:177:in `specs_for'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant.rb:76:in `<top (required)>'
    from /opt/vagrant/embedded/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:in `require'
    from /opt/vagrant/embedded/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:in `rescue in require'
    from /opt/vagrant/embedded/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:144:in `require'
    from /opt/vagrant/bin/../embedded/gems/gems/vagrant-1.7.2/bin/vagrant:105:in `<main>'

If I knew how, I would just nuke the whole installation from space and start over. Apparantly rm -rf /opt/vagrant is insufficient.

Also can this issue please be reopened?

[marblegravy]

@reinh - Try installing vagrant from the newest installers, then rm -rf ~/.vagrant.d
That worked for me.

The underlying cause is described better over in https://groups.google.com/forum/#!topic/vagrant-up/lpeay0kMaIU

[murdoc-mos]

Thanks @marblegravy, over a year later this answer is still relevant on 1.8.7

[GautamProtegrity]

$ vagrant up
Bundler, the underlying system used to manage Vagrant plugins,
is reporting that a plugin or its dependency can't be found.
This is usually caused by manual tampering with the 'plugins.json'
file in the Vagrant home directory. To fix this error, please
remove that file and reinstall all your plugins using vagrant plugin install.
C:/HashiCorp/Vagrant/embedded/gems/gems/bundler-1.10.5/lib/bundler/resolver.rb:347:in block in verify_gemfile_dependencies_are_found!': Could not find gem 'vagrant-vbguest (>= 0) x86-mingw32' in any of the gem sources listed in your Gemfile or available on this machine. (Bundler::GemNotFound) from C:/HashiCorp/Vagrant/embedded/gems/gems/bundler-1.10.5/lib/bundler/resolver.rb:325:ineach'
from C:/HashiCorp/Vagrant/embedded/gems/gems/bundler-1.10.5/lib/bundler/resolver.rb:325:in verify_gemfile_dependencies_are_found!' from C:/HashiCorp/Vagrant/embedded/gems/gems/bundler-1.10.5/lib/bundler/resolver.rb:198:instart'
from C:/HashiCorp/Vagrant/embedded/gems/gems/bundler-1.10.5/lib/bundler/resolver.rb:182:in resolve' from C:/HashiCorp/Vagrant/embedded/gems/gems/bundler-1.10.5/lib/bundler/definition.rb:200:inresolve'
from C:/HashiCorp/Vagrant/embedded/gems/gems/bundler-1.10.5/lib/bundler/definition.rb:140:in specs' from C:/HashiCorp/Vagrant/embedded/gems/gems/bundler-1.10.5/lib/bundler/definition.rb:185:inspecs_for'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant.rb:76:in <top (required)>' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:inrequire'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:in rescue in require' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:144:inrequire'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant:105:in `

'

Can anyone please help. I had already did this set up in windows 7 host that ran perfectly without any issues with virtual box 5.0. Used the same installer same, vbox version, same everything but it still soesn't work unable to figure out exactly whats wrong. Any command I type like 'vagrant up' / 'vagrant plugin install' or any such command starting with vagrant it gives this error. I have had no sleep, so please help

[Alphius1987]

I'm also stuck on this:
$ vagrant plugin install vagrant-proxyconf
Bundler, the underlying system used to manage Vagrant plugins,
is reporting that a plugin or its dependency can't be found.
This is usually caused by manual tampering with the 'plugins.json'
file in the Vagrant home directory. To fix this error, please
remove that file and reinstall all your plugins using vagrant plugin install.
C:/HashiCorp/Vagrant/embedded/gems/gems/bundler-1.10.6/lib/bundler/resolver.rb:347:in block in verify_gemfile_dependencies_are_found!': Could not find gem 'vagrant-proxyconf (>= 0) x86-mingw32' in any of the gem sources listed in your Gemfile or available on this machine. (Bundler::GemNotFound) from C:/HashiCorp/Vagrant/embedded/gems/gems/bundler-1.10.6/lib/bundler/resolver.rb:325:ineach'
from C:/HashiCorp/Vagrant/embedded/gems/gems/bundler-1.10.6/lib/bundler/resolver.rb:325:in verify_gemfile_dependencies_are_found!' from C:/HashiCorp/Vagrant/embedded/gems/gems/bundler-1.10.6/lib/bundler/resolver.rb:198:instart'
from C:/HashiCorp/Vagrant/embedded/gems/gems/bundler-1.10.6/lib/bundler/resolver.rb:182:in resolve' from C:/HashiCorp/Vagrant/embedded/gems/gems/bundler-1.10.6/lib/bundler/definition.rb:200:inresolve'
from C:/HashiCorp/Vagrant/embedded/gems/gems/bundler-1.10.6/lib/bundler/definition.rb:140:in specs' from C:/HashiCorp/Vagrant/embedded/gems/gems/bundler-1.10.6/lib/bundler/definition.rb:185:inspecs_for'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant.rb:76:in <top (required)>' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:inrequire'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in rescue in require' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:39:inrequire'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/bin/vagrant:105:in `

'

Any help is highly appreciated, thanks in advance

[SKempin]

rm -rf ~/.vagrant.d fixed this for me, on Windows 7.

[e-oloughlin]

On OSX 10.11.6 running vagrant 1.87, rm -rf ~/.vagrant.d worked for me... or in reality mv ~/.vagrant.d ~/.vagrant.d.backup ;)

[webfacer]

still not working for me on windows, i also deleted it and run new installtion with fresh vagrant install exe but still getting this errors

[hashibot[bot]]

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.