Bug 852295

Summary:	Rebalance status command does not respond if network is down or power failure on any of the nodes in the cluster
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Vidya Sakar <vinaraya>
Component:	glusterd	Assignee:	krishnan parthasarathi <kparthas>
Status:	CLOSED DUPLICATE	QA Contact:	Sudhir D <sdharane>
Severity:	high	Docs Contact:
Priority:	high
Version:	2.0	CC:	amarts, gluster-bugs, nsathyan, rfortier, rhs-bugs, shmohan, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	822784
Clones:	858476 (view as bug list)		Environment:
Last Closed:	2013-01-09 07:55:48 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:	822784
Bug Blocks:	858476

Description Vidya Sakar 2012-08-28 07:08:16 UTC

+++ This bug was initially created as a clone of Bug #822784 +++

Created attachment 585348 [details]
fsm logs

Description of problem:
Issuing rebalance status command does not responds if network fails or power failure occurs on any of the node in the cluster.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. created a distributed-replicate volume and fill up with some data
2. add-brick and initiate rebalance .
3. check the status 
4. Now bring down network or reboot any of the machine in the cluster
5. Now check the status
  
Actual results:

status command will not respond anything , it waits for some time and comes back with return value 234.

Expected results:


Additional info:

Attaching the fsm-logs.

--- Additional comment from amarts on 2012-07-11 01:22:22 EDT ---

shylesh, can you check if this happens on master/3.3.0 release?

--- Additional comment from shmohan on 2012-07-11 07:18:39 EDT ---

 (In reply to comment #1)
> shylesh, can you check if this happens on master/3.3.0 release?

Yes amar this issue is still reproducible on latest master.

Comment 2 krishnan parthasarathi 2013-01-09 07:55:48 UTC


*** This bug has been marked as a duplicate of bug 852147 ***