Bug 1049890

Summary: [RHSC] - Failed rebalance operation started automatically when glusterd is restarted.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: RamaKasturi <knarra>
Component: rhscAssignee: Shubhendu Tripathi <shtripat>
Status: CLOSED CANTFIX QA Contact: RamaKasturi <knarra>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.1CC: dtsang, knarra, mmahoney, rhs-bugs, sabose, sharne, shtripat, ssampat
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
When gluster daemon service is restarted, failed rebalance is started automatically and the status is displayed as 'Started' in the Red Hat Storage Console.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-26 06:13:54 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: 1035040    
Attachments:
Description Flags
engine logs none

Description RamaKasturi 2014-01-08 12:45:52 UTC 
Description of problem:
Failed rebalance operation started automatically when glusterd is restarted , by giving the event message as "Detected start of rebalance on volume <volName> of Cluster <clusterName> from CLI."

Version-Release number of selected component (if applicable):
rhsc-2.1.2-0.32.el6rhs.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create 10 distribute volumes .
2. Start rebalance on all the volumes at once.
3. Once rebalance is started on one volume, click on the status button, it fails to fetch status details.
4. On the same volume try fetching volume advanced details, it fails.
5. Now rebalance on the all the remaining volumes fails by giving an event message "Could not start Gluster Volume <volName> rebalance."
6. Now restart glusterd on all the nodes.

Actual results:
Rebalance starts automatically on the volumes where it failed by giving an event message "Detected start of rebalance on volume <volName> of Cluster <clusterName> from CLI".

Expected results:
Rebalance should not be started automatically when glusterd is restarted.

Additional info:
Comment 1 Shruti Sampat 2014-01-08 12:56:15 UTC 
Created attachment 847112 [details]
engine logs
Comment 4 Shalaka 2014-01-23 09:15:26 UTC 
Please review the edited DocText and signoff.
Comment 5 RamaKasturi 2014-01-24 06:55:35 UTC 
I am seeing this issue very often in my local config. Following are the steps i performed:

1) Created 2 distribue (say vol_dis and vol_dis1) and 2 distribute replicate volumes (say vol_dis_rep and vol_dis_rep1) using 4 RHS servers.

2) Now start rebalance on vol_dis and vol_dis1.

3) Bring down glusterd in one of the node and stop rebalance on vol_dis.

4) Rebalance is stopped and the status icon gets updated with rebalance stopped icon.

5) Now bring back glusterd in the node where it was stopped.

6) Now rebalance starts automatically in the volume vol_dis_rep, with  an event message  "Detected start of rebalance on volume vol_dis_rep of Cluster cluster_regress from CLI"
Comment 6 RamaKasturi 2014-01-24 07:40:57 UTC 
sos reports are attached here:

http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1049890/
Comment 7 Shubhendu Tripathi 2014-01-27 05:00:47 UTC 
doc text looks fine
Comment 8 Sahina Bose 2015-02-17 10:06:25 UTC 
Seems like a gluster issue and not an RHSC issue. Closing this as CANTFIX here. Please log a bug in gluster if required