Bug 1355610

Summary:	Fix timing issue in tests/bugs/glusterd/bug-963541.t
Product:	[Community] GlusterFS	Reporter:	Sakshi <sabansal>
Component:	tests	Assignee:	Satish Mohan <smohan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.8.1	CC:	bugs, smohan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1354372	Environment:
Last Closed:	2016-08-12 09:47:17 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:
Bug Depends On:	1354372, 1375049
Bug Blocks:

Description Sakshi 2016-07-12 05:07:06 UTC

+++ This bug was initially created as a clone of Bug #1354372 +++

Description of problem:
Start and stop rebalance, but the stop command fails as by that time the rebalance process has not come up.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:


Additional info:
RCA: on starting rebalance, the process had not come up because glusterd spawns it with nowait from runner interface. So the rebalance stop issued fails

--- Additional comment from Vijay Bellur on 2016-07-11 04:07:44 EDT ---

REVIEW: http://review.gluster.org/14885 (tests: fix rebalance timing issue) posted (#1) for review on master by Sakshi Bansal

--- Additional comment from Vijay Bellur on 2016-07-11 10:05:01 EDT ---

COMMIT: http://review.gluster.org/14885 committed in master by Jeff Darcy (jdarcy) 
------
commit bfbadab0d65f38d2719ceb4d5c9144377db9d4d5
Author: Sakshi Bansal <sabansal>
Date:   Mon Jul 11 13:34:28 2016 +0530

    tests: fix rebalance timing issue
    
    With a start and stop rebalance, the stop command may fail
    as by that time the rebalance process may not come up.
    Using the rebalance status commmand to ensure that the rebalance
    process is up before stoping rebalance.
    
    Change-Id: I3d5123cd5dfabde2720428455b257d11b980ce21
    BUG: 1354372
    Signed-off-by: Sakshi Bansal <sabansal>
    Reviewed-on: http://review.gluster.org/14885
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Jeff Darcy <jdarcy>

Comment 1 Vijay Bellur 2016-07-12 05:11:09 UTC

REVIEW: http://review.gluster.org/14897 (tests: fix rebalance timing issue) posted (#1) for review on release-3.8 by Sakshi Bansal

Comment 2 Vijay Bellur 2016-07-21 11:04:39 UTC

COMMIT: http://review.gluster.org/14897 committed in release-3.8 by Atin Mukherjee (amukherj) 
------
commit 54e7397505f0a6b218ab70415420371a5755ef0d
Author: Sakshi Bansal <sabansal>
Date:   Mon Jul 11 13:34:28 2016 +0530

    tests: fix rebalance timing issue
    
    With a start and stop rebalance, the stop command may fail
    as by that time the rebalance process may not come up.
    Using the rebalance status commmand to ensure that the rebalance
    process is up before stoping rebalance.
    
    Backport of http://review.gluster.org/14885
    
    > Change-Id: I3d5123cd5dfabde2720428455b257d11b980ce21
    > BUG: 1354372
    > Signed-off-by: Sakshi Bansal <sabansal>
    > Reviewed-on: http://review.gluster.org/14885
    > Smoke: Gluster Build System <jenkins.org>
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    > CentOS-regression: Gluster Build System <jenkins.org>
    > Reviewed-by: Jeff Darcy <jdarcy>
    
    Change-Id: I3d5123cd5dfabde2720428455b257d11b980ce21
    BUG: 1355610
    Signed-off-by: Sakshi Bansal <sabansal>
    Reviewed-on: http://review.gluster.org/14897
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Atin Mukherjee <amukherj>

Comment 5 Niels de Vos 2016-08-12 09:47:17 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-3.8.2, please open a new bug report.

glusterfs-3.8.2 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://www.gluster.org/pipermail/announce/2016-August/000058.html
[2] https://www.gluster.org/pipermail/gluster-users/