Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1526780

Summary: ./run-tests-in-vagrant.sh fails because of disabled Gluster/NFS
Product: [Community] GlusterFS Reporter: Niels de Vos <ndevos>
Component: testsAssignee: Niels de Vos <ndevos>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-5.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-23 15:06:35 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 Niels de Vos 2017-12-17 12:31:01 UTC
Description of problem:
gNFS has been deprecated a while ago, but the ./run-tests-in-vagrant.sh
script has not been adapted to enable it. This causes the tests to fail
the first time a Gluster Volume is mounted over NFSv3.

Version-Release number of selected component (if applicable):
everything from 3.11 onwards where gnfs is not enabled by default anymore

How reproducible:
100%

Steps to Reproduce:
1. run ./run-tests-in-varant.sh

Actual results:
Tests fail.

Expected results:
Tests pass.

Comment 1 Worker Ant 2017-12-22 06:13:23 UTC
COMMIT: https://review.gluster.org/19041 committed in master by \"Niels de Vos\" <ndevos> with a commit message- tests/vagrant: configure with --enable-gnfs so tests can use NFS

gNFS has been deprecated a while ago, but the ./run-tests-in-vagrant.sh
script has not been adapted to enable it. This causes the tests to fail
the first time a Gluster Volume is mounted over NFSv3.

Change-Id: Ifeec0ca964680ff61b956a5592a76eeee8ac3b85
BUG: 1526780
Signed-off-by: Niels de Vos <ndevos>

Comment 2 Worker Ant 2017-12-25 13:38:07 UTC
REVIEW: https://review.gluster.org/19073 (tests/vagrant: add a --help option to the script) posted (#1) for review on master by Niels de Vos

Comment 3 Worker Ant 2017-12-27 11:31:33 UTC
COMMIT: https://review.gluster.org/19073 committed in master by \"Niels de Vos\" <ndevos> with a commit message- tests/vagrant: add a --help option to the script

Change-Id: I89913375fedb6a7617873b09039de72bf1773c68
BUG: 1526780
Signed-off-by: Niels de Vos <ndevos>

Comment 4 Shyamsundar 2018-03-15 11:24:00 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-4.0.0, please open a new bug report.

glusterfs-4.0.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2018-March/000092.html
[2] https://www.gluster.org/pipermail/gluster-users/

Comment 5 Worker Ant 2018-06-14 12:17:55 UTC
REVIEW: https://review.gluster.org/19042 (tests/vagrant: install additional dependencies) posted (#2) for review on master by Niels de Vos

Comment 6 Worker Ant 2018-06-19 11:50:58 UTC
COMMIT: https://review.gluster.org/19042 committed in master by "Raghavendra Talur" <rtalur> with a commit message- tests/vagrant: install additional dependencies

The Vagrant box that is used by ./run-tests-in-vagrant.sh does not have
all recent dependencies installed. By using 'dnf builddep' to install
the BuildRequires from the generated .spec file, most future problems
should be prevented.

The tests/basic/afr/split-brain-favorite-child-policy.t script uses the
'bc' command. This it a run-time dependency for the test, and will not
be found with 'dnf builddep'.

Change-Id: Ifdbfc4af2997ea27815126766cc093947ddf523f
BUG: 1526780
Signed-off-by: Niels de Vos <ndevos>

Comment 7 Shyamsundar 2018-10-23 15:06:35 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report.

glusterfs-5.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/