Bug 1532591

Summary:	Tests: Geo-rep tests are failing in few regression machines
Product:	[Community] GlusterFS	Reporter:	Kotresh HR <khiremat>
Component:	geo-replication	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra, mscherer, nigelb, ravishankar
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-4.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-15 11:24:53 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 Kotresh HR 2018-01-09 12:02:21 UTC

Description of problem:
Geo-replication regression tests (tests/geo-rep/georep-basic-dr-rsync.t) are failing in few of the machines with gluster version mismatch. e.g.
https://build.gluster.org/job/centos6-regression/8298/consoleFull

The reason is the gluster binary path is not exported in .bashrc in all the machines.

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


How reproducible:
Always in few machines



Actual results:


Expected results:


Additional info:

Comment 1 Ravishankar N 2018-01-10 02:17:16 UTC

Adding myself to the CC list to be notified of the fix. My patch https://review.gluster.org/#/c/19070/ is blocked because of this, as every 'recheck centos' is causing this .t to fail on the slaves.

Comment 2 M. Scherer 2018-01-10 15:22:34 UTC

I pushed a fix that add the path to the various linux servers. I am not sure if we need to disconnect/reconnect jenkins to pick the change, and since centos 6 tests are failling for others reasons, I will first fix that and later see if my fix for georep was sufficient.

Comment 3 Ravishankar N 2018-01-11 09:51:23 UTC

Hi Michael, Is it okay to 'recheck centos' on my patch now? Or should I rebase it to re-trigger the regression?

Comment 4 Nigel Babu 2018-01-11 10:58:10 UTC

The changes were at the infra level. You can do a recheck centos on your patch without rebase.

Comment 5 Worker Ant 2018-01-18 06:17:24 UTC

REVIEW: https://review.gluster.org/19224 (geo-rep: Validate availability of gluster binary on slave) posted (#1) for review on master by Kotresh HR

Comment 6 Worker Ant 2018-01-19 03:53:56 UTC

COMMIT: https://review.gluster.org/19224 committed in master by \"Kotresh HR\" <khiremat> with a commit message- geo-rep: Validate availability of gluster binary on slave

1. Adds validation to check if gluster binary is available on slave
2. Add a simple geo-rep setup test case to verify whether setup is fine.
   It's named in such a way that it runs first.

BUG: 1532591
Change-Id: Ie777e55ae13db8fa97d4e32464ad82269ee5fd07
Signed-off-by: Kotresh HR <khiremat>

Comment 7 Shyamsundar 2018-03-15 11:24:53 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/