Bug 1811217

Summary:	vagrant 2.2.6 is incompatible with latest package for VirtualBox (6.1). Update vagrant to 2.2.7
Product:	[Fedora] Fedora	Reporter:	dan
Component:	vagrant	Assignee:	Pavel Valena <pvalena>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	31	CC:	lmohanty, madam, philbates35, pvalena, strzibny, thrcka, vondruch
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-10 18:12:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description dan 2020-03-06 21:22:00 UTC

Description of problem:
The latest Vagrant package 2.2.6 provided by the @System repository on Fedora 31 is not compatible with the latest VirtualBox v6.1 package provided by the @System repository. 2.2.6 is only compatible with VirtualBox <=6.0


Version-Release number of selected component (if applicable):
2.2.6


How reproducible:


Steps to Reproduce:
1. Execute 'vagrant init ubuntu/bionic64'
2. Execute 'vagrant up'
3. Execute 'vagrant up --provider virtualbox'

Actual results:
'Vagrant up' fails with an error message
"The box you're attempting to add doesn't support the provider
you requested.

Name: ubuntu/bionic64
Address: https://vagrantcloud.com/ubuntu/bionic64
Requested provider: [:libvirt]"


'Vagrant up --provider virtualbox' provides the error message: 
"The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:

Vagrant has detected that you have a version of VirtualBox installed
that is not supported by this version of Vagrant. Please install one of
the supported versions listed below to use Vagrant:

4.0, 4.1, 4.2, 4.3, 5.0, 5.1, 5.2, 6.0"

Expected results:
Executing 'vagrant up' after 'vagrant init ubuntu/bionic64' should begin to set up a virtual server via VirtualBox using the Vagrantfile created by 'vagrant init'

Additional info:
None

Comment 1 dan 2020-03-06 21:29:35 UTC

The Vagrant 2.2.7 Changelog identifies the updated support for Version 6.1 of VirtualBox https://github.com/hashicorp/vagrant/blob/v2.2.7/CHANGELOG.md

Comment 2 Pavel Valena 2020-03-10 18:12:37 UTC

Yes, I'm working on updating to Vagrant 2.2.7, but there have been some issues in Rawhide, due to Ruby 2.7. (And you cannot have Rawhide version lower than F31.)

If you need a working setup now, please try my COPR repo as a temporary workaround:

  https://copr.fedorainfracloud.org/coprs/pvalena/vagrant/


Please also note that VirtualBox is not part of Fedora, but it's in rpmfusion instead. Therefore there are no guarantees to it working with Vagrant (rpmfusion is out of our scope).
You can try Libvirt instead:

  http://developer.fedorainfracloud.org/tools/vagrant/vagrant-libvirt.html