Description of problem: Updated to Fedora 34 beta, tried to run `vagrant up` on one project I contribute to, and it failed when trying to load rexml/document. How reproducible: Always Steps to Reproduce: 0. dnf install vagrant vagrant-libvirt 1. git clone https://github.com/mozsearch/mozsearch 2. cd mozsearch 3. vagrant up Actual results: $ vagrant up Bringing machine 'default' up with 'libvirt' provider... ==> default: Checking if box 'generic/ubuntu2004' version '3.2.6' is up to date... <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require': cannot load such file -- rexml/document (LoadError) from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require' from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.1.2/lib/vagrant-libvirt/action/start_domain.rb:2:in `<top (required)>' from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require' from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require' from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.1.2/lib/vagrant-libvirt/action.rb:50:in `block (2 levels) in action_up' from /usr/share/vagrant/gems/gems/vagrant-2.2.9/lib/vagrant/action/builtin/call.rb:47:in `call' from /usr/share/vagrant/gems/gems/vagrant-2.2.9/lib/vagrant/action/warden.rb:48:in `call' from /usr/share/vagrant/gems/gems/vagrant-2.2.9/lib/vagrant/action/builtin/box_check_outdated.rb:92:in `call' from /usr/share/vagrant/gems/gems/vagrant-2.2.9/lib/vagrant/action/warden.rb:48:in `call' from /usr/share/vagrant/gems/gems/vagrant-2.2.9/lib/vagrant/action/builtin/config_validate.rb:25:in `call' from /usr/share/vagrant/gems/gems/vagrant-2.2.9/lib/vagrant/action/warden.rb:48:in `call' from /usr/share/vagrant/gems/gems/vagrant-2.2.9/lib/vagrant/action/builder.rb:149:in `call' from /usr/share/vagrant/gems/gems/vagrant-2.2.9/lib/vagrant/action/runner.rb:89:in `block in run' from /usr/share/vagrant/gems/gems/vagrant-2.2.9/lib/vagrant/util/busy.rb:19:in `busy' from /usr/share/vagrant/gems/gems/vagrant-2.2.9/lib/vagrant/action/runner.rb:89:in `run' from /usr/share/vagrant/gems/gems/vagrant-2.2.9/lib/vagrant/machine.rb:240:in `action_raw' from /usr/share/vagrant/gems/gems/vagrant-2.2.9/lib/vagrant/machine.rb:212:in `block in action' from /usr/share/vagrant/gems/gems/vagrant-2.2.9/lib/vagrant/environment.rb:613:in `lock' from /usr/share/vagrant/gems/gems/vagrant-2.2.9/lib/vagrant/machine.rb:198:in `call' from /usr/share/vagrant/gems/gems/vagrant-2.2.9/lib/vagrant/machine.rb:198:in `action' from /usr/share/vagrant/gems/gems/vagrant-2.2.9/lib/vagrant/batch_action.rb:86:in `block (2 levels) in run' Expected results: Stuff works. Manually installing `rubygem-rexml` worked. Additional info:
Created attachment 1768344 [details] Another issue (same project) (This one I haven't yet figured out)
This might be related to ruby 3.0, iiuc: https://www.ruby-lang.org/en/news/2019/12/12/separation-of-positional-and-keyword-arguments-in-ruby-3-0/
So there are three issues in Fedora 34: * The dependency issue reported in comment 0. * Two other issues (at least) related to ruby 3.0. I sent PRs for the later two here: https://github.com/hashicorp/vagrant/pull/12273 / https://github.com/vagrant-libvirt/vagrant-libvirt/pull/1242
(In reply to Emilio Cobos Álvarez (:emilio) from comment #0) This was already reported in bug 1915671. However, I'll keep this open, because you are pointing another issues.
I haven't seen the other two problems, but https://github.com/hashicorp/vagrant/pull/12273 also occurs when trying to "vagrant up" an instance of Laravel Homestead with VirtualBox. While I wait for the PR to be merged, is it possible to downgrade ruby to an earlier version in Fedora 34 without breaking stuff?
Isn't it possible to apply Emilio's patch on the Fedora package of Vagrant? I can't execute 'vagrant up' as well, which is breaking it completely.
I'll be updating Vagrant in Fedora this week.
*** Bug 1959350 has been marked as a duplicate of this bug. ***
FEDORA-2021-17ded5c4ca has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-17ded5c4ca
FEDORA-2021-17ded5c4ca has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-17ded5c4ca` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-17ded5c4ca See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
That fixes the issue for me - Thanks!
FEDORA-2021-17ded5c4ca has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.