Bug 1177134 - glusterd: when there is loss in server quorum then it should block all operation
Summary: glusterd: when there is loss in server quorum then it should block all operation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: RHGS 3.0.4
Assignee: Gaurav Kumar Garg
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1177132
Blocks: 1182947
TreeView+ depends on / blocked
 
Reported: 2014-12-24 11:06 UTC by Gaurav Kumar Garg
Modified: 2016-06-05 23:38 UTC (History)
9 users (show)

Fixed In Version: glusterfs-3.6.0.44-1
Doc Type: Bug Fix
Doc Text:
Previously, glusterd did not check server quorum validation for few operation like add-brick, remove-brick, volume set command etc. Due to this, when there was a loss in server quorum, few operations (add-brick, remove-brick, volume set command etc.) passed successfully without checking for server quorum validation. With this fix, the server quorum validation is performed and as a result it will block all operations (except volume set <quorum options> and "volume reset all" commands) when there is a loss in server quorom.
Clone Of: 1177132
Environment:
Last Closed: 2015-03-26 06:35:06 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0682 0 normal SHIPPED_LIVE Red Hat Storage 3.0 enhancement and bug fix update #4 2015-03-26 10:32:55 UTC

Description Gaurav Kumar Garg 2014-12-24 11:06:56 UTC 
+++ This bug was initially created as a clone of Bug #1177132 +++

Description of problem:
when there is loss in quorum then it should block all the operation. currently we are able to do few operation for eg. volume set, add-brick, remove-brick when there is loss in quorum. 

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

How reproducible:
Almost always

Steps to Reproduce:
1. Create distribute volume with two node in cluster.
2. do gluster volume set 
    cluster.server-quorum-type: server
3. set quorum ratio
    cluster.server-quorum-ratio: 51
4. bring down any one of the node in cluster
2. perform add-brick, volume set, remove-brick operation in node which is currently active.
3. Its allowing these operation even there is loss in quorum.

Actual results:

Its successfully allowing these operation even if there is loss in quorum

Expected results:

It should give error and should not allow any operation when quorum is not met.
Comment 2 Atin Mukherjee 2015-01-21 04:39:20 UTC 
We have identified this issue as a MUST_FIX under 3.0.4 bucket, moving the milestone to 3.0.4.
Comment 3 SATHEESARAN 2015-01-21 05:54:36 UTC 
Providing qa_ack for this bug as this could be verified with 3.0.4 release timeline
Comment 4 SATHEESARAN 2015-02-19 08:09:31 UTC 
Following are the rejected Operations when server quorum is not met :

volume stop
volume rebalance
volume add-brick
volume remove-brick
volume remove-brick force
volume set ( test for all currently available options, except for quorum )
volume delete ( only when the volume is set with server-side quorum )

volume create operation is still allowed and tracked under this bug - https://bugzilla.redhat.com/show_bug.cgi?id=1194108

Marking this bug as VERIFIED
Comment 5 SATHEESARAN 2015-02-19 08:13:15 UTC 
Missed the verification build related information in comment4
This bug was verified with glusterfs-3.6.0.45-1.el6rhs
Comment 7 Bhavana 2015-03-24 04:38:39 UTC 
Hi gaurav,

The doc text is updated. review the same and sign off if it looks ok.
Comment 8 Gaurav Kumar Garg 2015-03-24 10:48:02 UTC 
Hi Bhavana,

doc text looks good to me. i have done little bit modification. review the same and sign off it it looks ok.
Comment 9 Bhavana 2015-03-25 12:08:56 UTC 
Thanks. Changing the doc text flag to +
Comment 11 errata-xmlrpc 2015-03-26 06:35:06 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.

https://rhn.redhat.com/errata/RHBA-2015-0682.html
Note You need to log in before you can comment on or make changes to this bug.