Bug 917000

Summary:	[RHSC] RFE: Generate an alert for the user, when a volume becomes unusable after 'gluster peer detach force'
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Shruti Sampat <ssampat>
Component:	rhsc	Assignee:	Sahina Bose <sabose>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Shruti Sampat <ssampat>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.1	CC:	dpati, dtsang, kmayilsa, knarra, mmahoney, rhs-bugs, ssampat
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-23 13:00:14 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:

Description Shruti Sampat 2013-03-01 12:05:17 UTC

Description of problem:
---------------------------------------
In a cluster of two nodes, one of the nodes is removed using "peer detach force".
For a volume that had a brick on each of the two servers, the Console now shows only one brick (the one on the detached server is no longer seen on the Console). On trying to start the volume, start fails.

It would be good to inform the user via an alert, that this volume cannot be started as it has bricks on nodes that are not part of the cluster.

Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 2.1.0-0.qa6.el6rhs 

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 3 Sahina Bose 2015-02-17 09:19:48 UTC

Is peer detach force possible now if there are bricks?

Comment 4 Shruti Sampat 2015-03-23 11:30:30 UTC

`gluster peer detach force' does not detach the peer if bricks exist on that peer. This is the current behavior (glusterfs 3.6.0.53). I think this BZ can be closed now.

Comment 5 Sahina Bose 2015-03-23 13:00:14 UTC

Marking this closed as per changed behaviour of glusterfs mentioned in Comment 4