Bug 1428839

Summary:	run-tests-in-vagrant.sh does not work on Ubuntu
Product:	[Community] GlusterFS	Reporter:	nh2 <nh2-redhatbugzilla>
Component:	tests	Assignee:	Raghavendra Talur <rtalur>
Status:	CLOSED EOL	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.10	CC:	bugs, nh2-redhatbugzilla
Target Milestone:	---	Keywords:	Triaged
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:	2018-06-20 18:29:31 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 nh2 2017-03-03 13:21:03 UTC

The Fedora box used in run-tests-in-vagrant.sh only supports libvirt as virtualisation provider, but for some reason vagrant on Ubuntu 16.04 (and potentially other OSs or versions of vagrant) picks Virtualbox as provider even if the box does not support it.

We can fix that with the following patch, speciftying `--provier libvirt` explicitly:

diff --git a/run-tests-in-vagrant.sh b/run-tests-in-vagrant.sh
index 162b689..f5053a2 100755
--- a/run-tests-in-vagrant.sh
+++ b/run-tests-in-vagrant.sh
@@ -137,7 +137,7 @@ function start_vm()
 {
     echo "Doing vagrant up...."
     pushd "tests/vagrant/${BRANCHNAME}"
-    eval vagrant up $redirect
+    eval vagrant up --provider libvirt $redirect
     if [ $? -eq 0 ]
     then
             popd

Comment 1 Shyamsundar 2018-06-20 18:29:31 UTC

This bug reported is against a version of Gluster that is no longer maintained
(or has been EOL'd). See https://www.gluster.org/release-schedule/ for the
versions currently maintained.

As a result this bug is being closed.

If the bug persists on a maintained version of gluster or against the mainline
gluster repository, request that it be reopened and the Version field be marked
appropriately.