Red Hat Bugzilla – Bug 1262230
[quorum]: Replace brick is happened when Quorum not met.
Last modified: 2018-09-04 02:29:06 EDT
Description of problem: Brick replace is happened successfully when Quorum not met also which is not expected. Version-Release number of selected component (if applicable): glusterfs-3.7.1-14 How reproducible: Always Steps to Reproduce: 1.Create a cluster of two nodes (Node-1 and Node-2) 2.Create a Distributed volume using two node bricks. 3.Start the Volume. 4.Shutdown one of the node (Node-2) 5. a. Check the volume status //brick status should be offline (To make sure Quorum Not met ) (OR) b. Check for message "Server quorum lost for volume Dis. Stopping local bricks." in /var/log/messages 6. Replace the existing brick on node which is up with new brick. Actual results: Replace brick is happened when quorum not met Expected results: Replace brick should not happen when quorum not met. Additional info:
Created attachment 1072494 [details] Glusterd Log
This issue reproduced with 3.1.2 build (glusterfs-3.7.5-15 ) as well.
upstream patch : https://review.gluster.org/18068
BUILD : 3.12.2-4 When quorum is not met, replace brick is failing as expected. Hence marking it as verified
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://access.redhat.com/errata/RHSA-2018:2607