Bug 1375049 - Fix timing issue in tests/bugs/glusterd/bug-963541.t
Summary: Fix timing issue in tests/bugs/glusterd/bug-963541.t
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: tests
Version: 3.7.15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Atin Mukherjee
QA Contact:
URL:
Whiteboard:
Depends On: 1354372
Blocks: 1355610
TreeView+ depends on / blocked
 
Reported: 2016-09-12 04:26 UTC by Atin Mukherjee
Modified: 2016-10-17 09:05 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.7.16
Clone Of: 1354372
Environment:
Last Closed: 2016-10-17 09:05:14 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Atin Mukherjee 2016-09-12 04:26: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>

--- Additional comment from John Skeoch on 2016-07-31 21:22:51 EDT ---

User sabansal's account has been closed

--- Additional comment from John Skeoch on 2016-07-31 21:24:17 EDT ---

User sabansal's account has been closed

Comment 1 Worker Ant 2016-09-12 04:27:24 UTC
REVIEW: http://review.gluster.org/15461 (tests: fix rebalance timing issue) posted (#1) for review on release-3.7 by Atin Mukherjee (amukherj)

Comment 2 Worker Ant 2016-09-19 05:35:24 UTC
COMMIT: http://review.gluster.org/15461 committed in release-3.7 by Kaushal M (kaushal) 
------
commit 801cdb1e2381b988b515819f02120cd129fc4740
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.
    
    >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: 1375049
    Signed-off-by: Atin Mukherjee <amukherj>
    Reviewed-on: http://review.gluster.org/15461
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Kaushal M <kaushal>

Comment 3 Kaushal 2016-10-17 09:05:14 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.7.16, please open a new bug report.

glusterfs-3.7.16 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://www.gluster.org/pipermail/gluster-devel/2016-October/051187.html
[2] https://www.gluster.org/pipermail/gluster-users/


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