vagrant-aws
vagrant-aws copied to clipboard
Cannot install plugin on Ubuntu 16.04 with vagrant 1.9.0
I have a fresh install of Ubuntu 16.04, and I grabbed the latest vagrant (appears to be 1.9.0) from the install page. Can't install AWS plugin:
$ vagrant plugin install --verbose vagrant-aws
Installing the 'vagrant-aws' plugin. This can take a few minutes...
/opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/dependency.rb:315:in `to_specs': Could not find 'fog-xml' (>= 0) among 45 total gem(s) (Gem::LoadError)
Checked in 'GEM_PATH=/opt/vagrant/embedded/gems', execute `gem env` for more information
from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/specification.rb:1311:in `block in activate_dependencies'
from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/specification.rb:1300:in `each'
from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/specification.rb:1300:in `activate_dependencies'
from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/specification.rb:1282:in `activate'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/bundler.rb:319:in `block in activate_solution'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/bundler.rb:316:in `each'
...
Also doesn't work with the vagrant package that comes with Ubuntu 16.04 (version 1.8.1):
$ vagrant plugin install --verbose vagrant-aws
Installing the 'vagrant-aws' plugin. This can take a few minutes...
Warning: this Gemfile contains multiple primary sources. Using `source` more than once without a block is a security risk, and may result in installing unexpected gems. To resolve this warning, use a block to indicate which gems should come from the secondary source. To upgrade this warning to an error, run `bundle config disable_multisource true`.
/usr/lib/ruby/2.3.0/rubygems/specification.rb:946:in `all=': undefined method `group_by' for nil:NilClass (NoMethodError)
from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:275:in `with_isolated_gem'
from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:231:in `internal_install'
from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:102:in `install'
from /usr/lib/ruby/vendor_ruby/vagrant/plugin/manager.rb:62:in `block in install_plugin'
from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:173:in `block in verbose'
from /usr/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize'
...
Am I doing something wrong here?
UPDATE: that one is a known issue (http://stackoverflow.com/questions/36811863/cant-install-vagrant-plugins-in-ubuntu-16-04/36991648#36991648).
I am having the same issue on Windows 10 using Vagrant 1.9.0 (vagrant_1.9.0.msi):
C:\Users\row\Tools\Console2>vagrant plugin install vagrant-aws
Installing the 'vagrant-aws' plugin. This can take a few minutes...
C:/Users/row/Tools/Vagrant/embedded/lib/ruby/2.2.0/rubygems/dependency.rb:315:in `to_specs': Could not find 'fog-xml' (>= 0) among 45 total gem(s) (Gem::LoadError)
Checked in 'GEM_PATH=C:/Users/row/Tools/Vagrant/embedded/gems', execute `gem env` for more information
from C:/Users/row/Tools/Vagrant/embedded/lib/ruby/2.2.0/rubygems/specification.rb:1311:in `block in activate_dependencies'
from C:/Users/row/Tools/Vagrant/embedded/lib/ruby/2.2.0/rubygems/specification.rb:1300:in `each'
from C:/Users/row/Tools/Vagrant/embedded/lib/ruby/2.2.0/rubygems/specification.rb:1300:in `activate_dependencies'
from C:/Users/row/Tools/Vagrant/embedded/lib/ruby/2.2.0/rubygems/specification.rb:1282:in `activate'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/bundler.rb:319:in `block in activate_solution'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/bundler.rb:316:in `each'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/bundler.rb:316:in `activate_solution'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/bundler.rb:244:in `internal_install'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/bundler.rb:97:in `install'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/plugin/manager.rb:62:in `block in install_plugin'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/plugin/manager.rb:72:in `call'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/plugin/manager.rb:72:in `install_plugin'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/plugins/commands/plugin/action/install_gem.rb:37:in `call'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/warden.rb:34:in `call'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/builder.rb:116:in `call'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/runner.rb:66:in `block in run'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/util/busy.rb:19:in `busy'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/runner.rb:66:in `run'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/plugins/commands/plugin/command/base.rb:14:in `action'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/plugins/commands/plugin/command/install.rb:32:in `block in execute'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/plugins/commands/plugin/command/install.rb:31:in `each'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/plugins/commands/plugin/command/install.rb:31:in `execute'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/plugins/commands/plugin/command/root.rb:66:in `execute'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/cli.rb:42:in `execute'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/environment.rb:308:in `cli'
from C:/Users/row/Tools/Vagrant/embedded/gems/gems/vagrant-1.9.0/bin/vagrant:123:in `<main>'
It looks like ssl certificate verification is failing when the embedded gem binary tries to contact rubygems.org. I followed this and was able to get a new .pem file in place that fixed the verification failures, but I'm still not able to get it to install (it might be missing pkg-config or libiconv headers, or I don't have the path set up correctly)
@dsyer I'm having this exact same issue on macOS sierra, with vagrant 1.9.0.
While it's being fixed: https://releases.hashicorp.com/vagrant/1.8.7/
You may want to install vagrant 1.8.6 instead. There are issues with 1.8.7.
Having the same problem here. Very frustrating if you assume that getting the latest version will get you the best-working version
/opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/dependency.rb:315:in `to_specs': Could not find 'fog-xml' (>= 0) among 45 total gem(s) (Gem::LoadError)
Even when I put the fog-xml gem where Vagrant appears to be looking, it STILL can't find it. :-/
Confirmed broken on macOS sierra also.
Running into same problem here with Vagrant 1.9.0 in a Rhel 7.3. Tried going back to Vagrant 1.8.7 and 1.8.6. It still happens (fog-xml error) ! May be something permanently messed up in my attempts to get 1.9 working !?
Confirm the same issue on ArchLinux, Vagrant 1.9.0
$ vagrant plugin install vagrant-aws
I get
/opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/dependency.rb:315:in `to_specs': Could not find 'fog-xml' (>= 0) among 44 total gem(s) (Gem::LoadError)
Checked in 'GEM_PATH=/opt/vagrant/embedded/gems', execute `gem env` for more information
...
Is there any solution here? I am having the same issue on 'CentOS Linux release 7.3.1611'.