I was running fine with Vagrant 2.4.1, but now after upgrading Vagrant 2.4.2, Vagrant no longer functions. I reported this as: Bricked Vagrant 2.4.2 environment after upgrade · Issue #13538 · hashicorp/vagrant · GitHub
It seems that there are gem incompatibilities and problem with vagrant-qemu. I read that Vagrant 2.4.2 broke vagrant-libvrt is broken as well.
These are important plugins, as vagrant-qemu is required for running on ARM64 Macbooks. For Linux and KVM, vagrant-libvrt is important as well.
Maybe version should be rolled back and removed until incompatibilities are worked out? My whole environment is not recoverable; I tried the vagrant plugin commands, I get messages about incompatible logger gem, and the environment is inoperable, essentially bricked.
I’m experiencing the same issue after upgrading to Vagrant 2.4.2! Everything was running perfectly fine with 2.4.1, but now after the update, my environment is completely bricked. Like you, I’m seeing the gem incompatibilities and issues with both vagrant-qemu and vagrant-libvirt. These plugins are essential for my setup, especially for ARM64 Macs and KVM-based Linux environments.
I’ve tried reinstalling the plugins and running vagrant plugin update, but it just keeps throwing errors about incompatible gems (especially the logger gem). It’s a mess right now. I agree that rolling back to Vagrant 2.4.1 might be the best short-term solution until the issues with 2.4.2 are resolved. Hopefully, the team will release a patch soon, as this version seems to have introduced some critical regressions. Would love to know if anyone has found a more immediate fix!
1 Like
It seems that Hashicorp no longer has staff that monitors these forums. I posted on X/Twitter, and no one seems to be monitoring those channels either.
There’s a documented workaround (src):
export VAGRANT_DISABLE_STRICT_DEPENDENCY_ENFORCEMENT=1
Other bugs/issues on GitHub:
This versions should not have been released, and needs an immediate rollback. New release should have rc or beta designation.