Bug 862017

Summary:	quorum is not restored when a server is removed from the cluster
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Sachidananda Urs <sac>
Component:	glusterd	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED ERRATA	QA Contact:	Sudhir D <sdharane>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.0	CC:	amarts, rhs-bugs, shaines, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.3.0.5rhs-36	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-23 22:39:15 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:	840122, 874018

Description Sachidananda Urs 2012-10-01 15:36:05 UTC

Description of problem:

Consider a scenario where the quorum ratio is set to 100%. And one of the server goes down... and quorum is lost and the bricks are killed.

Now we peer detach that server with force. Quorum should be restored, but it doesn't.

Comment 2 Amar Tumballi 2012-10-08 07:09:26 UTC

pranith already has the patch submitted for this..

Comment 3 Sachidananda Urs 2012-11-07 09:36:36 UTC

Verified with newer release. When the disconnected peer is deprobed, quorum is restored.

Comment 4 Scott Haines 2013-09-23 22:39:15 UTC

Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1262.html

Comment 5 Scott Haines 2013-09-23 22:43:42 UTC

Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1262.html