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):
Steps to Reproduce:
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
REVIEW: http://review.gluster.org/14885 (tests: fix rebalance timing issue) posted (#1) for review on master by Sakshi Bansal
COMMIT: http://review.gluster.org/14885 committed in master by Jeff Darcy (email@example.com)
Author: Sakshi Bansal <firstname.lastname@example.org>
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.
Signed-off-by: Sakshi Bansal <email@example.com>
Smoke: Gluster Build System <firstname.lastname@example.org>
NetBSD-regression: NetBSD Build System <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Jeff Darcy <email@example.com>
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.9.0, please open a new bug report.
glusterfs-3.9.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.