Bug 1330208 - vagrant plugin install gives error
Summary: vagrant plugin install gives error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: vagrant
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vít Ondruch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-25 15:52 UTC by Dusty Mabe
Modified: 2016-05-07 11:43 UTC (History)
5 users (show)

Fixed In Version: vagrant-1.8.1-2.fc24
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-07 11:43:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dusty Mabe 2016-04-25 15:52:49 UTC
Description of problem:
Error when running vagrant plugin install on F24. 

Upstream issue: https://github.com/mitchellh/vagrant/issues/7073
Upstream patch: https://github.com/mitchellh/vagrant/pull/7198

Can we carry this patch for the F24 release? 

Version-Release number of selected component (if applicable):
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


How reproducible:
Always

Steps to Reproduce:
1. Download gem file
2. vagrant plugin install ./vagrant-sshfs-1.1.0.gem

Actual results:
$ vagrant plugin install ./vagrant-sshfs-1.1.0.gem                                                                                                                                                      
Installing the './vagrant-sshfs-1.1.0.gem' plugin. This can take a few minutes...
/usr/share/rubygems/rubygems/specification.rb:946:in `all=': undefined method `group_by' for nil:NilClass (NoMethodError)
        from /usr/share/vagrant/lib/vagrant/bundler.rb:268:in `with_isolated_gem'
        from /usr/share/vagrant/lib/vagrant/bundler.rb:126:in `install_local'
        from /usr/share/vagrant/lib/vagrant/plugin/manager.rb:47:in `install_plugin'
        from /usr/share/vagrant/plugins/commands/plugin/action/install_gem.rb:37:in `call'
        from /usr/share/vagrant/lib/vagrant/action/warden.rb:34:in `call'
        from /usr/share/vagrant/lib/vagrant/action/builder.rb:116:in `call'
        from /usr/share/vagrant/lib/vagrant/action/runner.rb:66:in `block in run'
        from /usr/share/vagrant/lib/vagrant/util/busy.rb:19:in `busy'
        from /usr/share/vagrant/lib/vagrant/action/runner.rb:66:in `run'
        from /usr/share/vagrant/plugins/commands/plugin/command/base.rb:14:in `action'
        from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:32:in `block in execute'
        from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:31:in `each'
        from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:31:in `execute'
        from /usr/share/vagrant/plugins/commands/plugin/command/root.rb:56:in `execute'
        from /usr/share/vagrant/lib/vagrant/cli.rb:42:in `execute'
        from /usr/share/vagrant/lib/vagrant/environment.rb:302:in `cli'
        from /usr/share/vagrant/bin/vagrant:174:in `<main>'

Comment 1 Dusty Mabe 2016-04-30 03:08:24 UTC
Hi, Can we consider adding the patch to Fedora so that we don't drop users on their face when F24 is released?

Comment 2 Vít Ondruch 2016-05-02 08:42:21 UTC
I can reproduce on F25, so I'm going to apply the patch ...

Comment 3 Fedora Update System 2016-05-02 11:03:11 UTC
vagrant-1.8.1-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-302b1d18cf

Comment 4 Fedora Update System 2016-05-03 11:23:57 UTC
vagrant-1.8.1-2.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-302b1d18cf

Comment 5 Fedora Update System 2016-05-07 11:43:05 UTC
vagrant-1.8.1-2.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.