Bug 1095686

Summary:	When a brick is brought down, after a while it comes online automatically.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	RamaKasturi <knarra>
Component:	glusterd	Assignee:	krishnan parthasarathi <kparthas>
Status:	CLOSED ERRATA	QA Contact:	RamaKasturi <knarra>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	rhgs-3.0	CC:	dpati, kaushal, nlevinki, nsathyan, rhsc-qe-bugs, sasundar, ssamanta, vbellur
Target Milestone:	---	Keywords:	TestBlocker
Target Release:	RHGS 3.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.6.0-1.0.el6rhs.x86_64	Doc Type:	Bug Fix
Doc Text:	Cause: The server quorum framework in Glusterd would perform the quorum action (start or stop bricks) unconditionally on a quorum event, even if the new event did not cause the quorum status to change. Consequence: This could cause bricks which were taken down for maintenance to be started in the middle of maintenance. Fix: The current and previous quorum status are checked before attempting to start or stop bricks. Bricks are only started or stopped if the quorum status changed. Result: Bricks brought down for maintenance will no longer be started on spurious quorum events.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-22 19:37:00 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 RamaKasturi 2014-05-08 11:55:37 UTC

Description of problem:
When a brick is down, the brick comes up automatically after a while.

Version-Release number of selected component (if applicable):
Red Hat Storage Server 3.0
glusterfs-server-3.5qa2-0.450.gita05c579.el6rhs.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Create a volume by running the command "gluster vol create <vol_name> <brickpath>"
2. Now kill one of the brick in the volume by using the command "kill -9 <PID of brick>"
3.

Actual results:
Brick comes back online automatically.

Expected results:
Brick should not come  online automatically.

Additional info:

Comment 3 RamaKasturi 2014-05-13 11:35:21 UTC

Verified and works with build "glusterfs-3.6.0-1.0.el6rhs.x86_64".

When the brick is made down, it does not come online automatically.

Comment 4 Nagaprasad Sathyanarayana 2014-05-19 10:56:51 UTC

Setting flags required to add BZs to RHS 3.0 Errata

Comment 7 errata-xmlrpc 2014-09-22 19:37:00 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/RHEA-2014-1278.html