Description of problem: See this bug for more verbose description: https://bugzilla.redhat.com/show_bug.cgi?id=1330216 ``` $ vagrant plugin install ./vagrant-service-manager-1.0.1.gem Installing the './vagrant-service-manager-1.0.1.gem' 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: Could not find gem 'vagrant-service-manager (= 1.0.1) ruby' in any of the gem sources listed in your Gemfile or available on this machine. 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`. ``` Version-Release number of selected component (if applicable): - cdk-2.0.0.zip ced1ae9a5017c1cc70758eb9f57c933726a97852749b087eb966396f7b63ddf4 - vagrant-1.8.1-1.fc24.noarch - vagrant-libvirt-0.0.32-2.fc24.noarch - ruby-2.3.0-54.fc24.x86_64 - rubygems-2.5.1-54.fc24.noarch - rubygem-bundler-1.10.6-3.fc24.noarch
Thank you Dusty. FTR, this issue is resolved by https://github.com/mitchellh/vagrant/pull/7505/
vagrant-1.8.1-3.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-c79ecd0357
vagrant-1.8.1-3.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-c79ecd0357
vagrant-1.8.1-3.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
This problem appears to still exist. [bgsmith@PICO c7-atomic]$ more /etc/redhat-release Fedora release 24 (Twenty Four) [bgsmith@PICO c7-atomic]$ rpm -qa | grep -i vagrant vagrant-libvirt-0.0.32-2.fc24.noarch vagrant-1.8.1-3.fc24.noarch [bgsmith@PICO c7-atomic]$ bgsmith@PICO c7-2]$ vagrant suspend Ignoring json-2.0.2 because its extensions are not built. Try: gem pristine json --version 2.0.2 Ignoring json-2.0.2 because its extensions are not built. Try: gem pristine json --version 2.0.2 ==> default: Suspending domain... [bgsmith@PICO c7-2]$ vagrant plugin install vagrant-openstack-provider Ignoring json-2.0.2 because its extensions are not built. Try: gem pristine json --version 2.0.2 Ignoring json-2.0.2 because its extensions are not built. Try: gem pristine json --version 2.0.2 Installing the 'vagrant-openstack-provider' 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: An error occurred while installing ffi (1.9.14), and Bundler cannot continue. Make sure that `gem install ffi -v '1.9.14'` succeeds before bundling. 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`.Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
I don't think this is the same problem. This bug's issue is related to installing directly from local gem file. It looks like you are installing from rubygems. In my case I was getting a failure when installing from a local file: $ vagrant plugin install ./vagrant-service-manager-1.0.1.gem but when installing from rubygems it would succeed: $ vagrant plugin install vagrant-service-manager
Thanks. I agree. I resolved my problem (comment 5) by installing ruby-devel rpm.