Description of problem: After creating a new volume and executing Rebalance Stop Command (without issuing Rebalance Start Command), it gives the following message : Stopped rebalance process on volume test1 Version-Release number of selected component (if applicable): glusterfs-3.3.0.5rhs-40.el6rhs.x86_64 How reproducible: Always Steps to Reproduce: 1.Create a Distributed Volume with 2 bricks and start it 2.Run gluster volume rebalance $vol Stop 3. Actual results: gluster volume rebalance test1 stop Node Rebalanced-files size scanned failures status localhost 0 0 0 0 not started 10.70.34.86 0 0 0 0 not started 10.70.34.103 0 0 0 0 not started 10.70.34.105 0 0 0 0 not started Stopped rebalance process on volume test1 Expected results: "Stopped rebalance process on volume" message should not be displayed when a rebalance Stop command is issued on the volume when Rebalance has not been started . Additional info:
can be handled by setting the right op_errstr in stage/handle level of command.
Per Feb-06 bug triage meeting, targeting for 2.1.0.
The product version of Red Hat Storage on which this issue was reported has reached End Of Life (EOL) [1], hence this bug report is being closed. If the issue is still observed on a current version of Red Hat Storage, please file a new bug report on the current version. [1] https://rhn.redhat.com/errata/RHSA-2014-0821.html