Description of problem: Every command of vagrant fails with error: Traceback (most recent call last): 8: from /usr/share/vagrant/gems/bin/vagrant:23:in `<main>' 7: from /usr/share/rubygems/rubygems.rb:303:in `activate_bin_path' 6: from /usr/share/rubygems/rubygems.rb:303:in `synchronize' 5: from /usr/share/rubygems/rubygems.rb:304:in `block in activate_bin_path' 4: from /usr/share/rubygems/rubygems/specification.rb:1420:in `activate' 3: from /usr/share/rubygems/rubygems/specification.rb:1438:in `activate_dependencies' 2: from /usr/share/rubygems/rubygems/specification.rb:1438:in `each' 1: from /usr/share/rubygems/rubygems/specification.rb:1449:in `block in activate_dependencies' /usr/share/rubygems/rubygems/dependency.rb:313:in `to_specs': Could not find 'net-ssh' (~> 5.1.0) - did find: [net-ssh-5.2.0] (Gem::MissingSpecVersionError) Checked in 'GEM_PATH=/usr/share/gems:/usr/share/vagrant/gems:/home/vagrant/.vagrant.d/gems', execute `gem env` for more information (as seen in https://dashboard.zuul.ansible.com/t/ansible/build/1852c8c715b1487c859241c9b57db823/log/job-output.txt) This can be reproduced by launching a fresh fedora 31 system and try a vagrant command. I've used the vagrant box fedora/31-cloud-base but can probably be reproduced with other systems, since it's failing in ansible zuul CI. I guess it's the same as bug https://bugzilla.redhat.com/show_bug.cgi?id=1805240 which is marked as rawhide but it's valid for fedora 31 too. Version-Release number of selected component (if applicable): vagrant-2.2.6-1.fc31.noarch How reproducible: Steps to Reproduce: 1. Install fedora 31 2. Install vagrant 3. vagrant box add fedora/31-cloud-base 4. vagrant box list Actual results: /usr/share/rubygems/rubygems/dependency.rb:313:in `to_specs': Could not find 'net-ssh' (~> 5.1.0) - did find: [net-ssh-5.2.0] (Gem::MissingSpecVersionError) Expected results: vagrant box add fedora/31-cloud-base box: Successfully added box 'fedora/31-cloud-base' (v31.20191023.0) for ... vagrant box list fedora/31-cloud-base (libvirt, 31.20191023.0)
Hello, thank you for your report. I'm sorry, sadly I've missed the dependency breakage. To temporarily workaround this you can downgrade rubygem-net-ssh, or you can install this update with newer Vagrant: https://bodhi.fedoraproject.org/updates/FEDORA-2020-09c472786c.
Hi, I've tested in the ansible zuul CI your updated packages and the things are working now (job log https://dashboard.zuul.ansible.com/t/ansible/build/e5961956b63f475cb86d0169bafedec7/log/job-output.txt). Thanks
*** Bug 1844059 has been marked as a duplicate of this bug. ***
FEDORA-2020-09c472786c has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-09c472786c
FEDORA-2020-09c472786c has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
*** Bug 1844277 has been marked as a duplicate of this bug. ***
Thank you for handling this. It looks like it is working now. I just triggered "dnf update" with resutl: [ppolawsk@chopper]<~>$ sudo rpm -qa | grep rubygem-net-ssh rubygem-net-ssh-5.2.0-1.fc31.noarch [ppolawsk@chopper]<~>$ sudo rpm -qa | grep vagrant vagrant-2.2.9-1.fc31.noarch vagrant-libvirt-0.0.45-3.fc31.noarch I am able to use vagrant without any issues now. Bug can be closed.
(In reply to Paweł Poławski from comment #7) Thank you for feedback. Glad that works. The bug was already closed by Bodhi, so everything seems alright.