Bug 1428839 - run-tests-in-vagrant.sh does not work on Ubuntu
Summary: run-tests-in-vagrant.sh does not work on Ubuntu
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: tests
Version: 3.10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Raghavendra Talur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-03 13:21 UTC by nh2
Modified: 2018-06-20 18:29 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-06-20 18:29:31 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.