Bug 902618

Summary: Rebalance Stop Command does not give proper message
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: senaik
Component: distributeAssignee: Nithya Balachandran <nbalacha>
Status: CLOSED WONTFIX QA Contact: senaik
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0CC: amukherj, rhs-bugs, rwheeler, sdharane, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 914641 (view as bug list) Environment:
Last Closed: 2015-03-23 07:38:26 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:    
Bug Blocks: 914641    

Description senaik 2013-01-22 05:36:56 UTC 
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:
Comment 2 Amar Tumballi 2013-01-22 08:49:25 UTC 
can be handled by setting the right op_errstr in stage/handle level of command.
Comment 4 Scott Haines 2013-02-06 20:06:39 UTC 
Per Feb-06 bug triage meeting, targeting for 2.1.0.
Comment 5 Scott Haines 2013-02-06 20:10:07 UTC 
Per Feb-06 bug triage meeting, targeting for 2.1.0.
Comment 6 Vivek Agarwal 2015-03-23 07:38:26 UTC 
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
Comment 7 Vivek Agarwal 2015-03-23 07:39:49 UTC 
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