+++ This bug was initially created as a clone of Bug #1262230 +++ Description of problem: Brick replace is happened successfully when Quorum not met also which is not expected. 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.
REVIEW: https://review.gluster.org/18068 (glusterd: replace-brick executing successfully when quorum does not met) posted (#1) for review on master by Gaurav Yadav (gyadav)
REVIEW: https://review.gluster.org/18068 (glusterd: replace-brick executing successfully when quorum does not met) posted (#2) for review on master by Gaurav Yadav (gyadav)
REVIEW: https://review.gluster.org/18068 (glusterd: replace-brick executing successfully when quorum does not met) posted (#3) for review on master by Gaurav Yadav (gyadav)
REVIEW: https://review.gluster.org/18068 (glusterd: replace-brick executing successfully when quorum does not met) posted (#4) for review on master by Gaurav Yadav (gyadav)
REVIEW: https://review.gluster.org/18068 (glusterd: replace-brick executing successfully when quorum does not met) posted (#5) for review on master by Gaurav Yadav (gyadav)
REVIEW: https://review.gluster.org/18068 (glusterd: replace-brick executing successfully when quorum does not met) posted (#6) for review on master by Gaurav Yadav (gyadav)
COMMIT: https://review.gluster.org/18068 committed in master by Atin Mukherjee (amukherj) ------ commit 5f3ff9b33c286b30f2c6d2fadf53757b9f48859e Author: Gaurav Yadav <gyadav> Date: Fri Aug 18 23:06:13 2017 +0530 glusterd: replace-brick executing successfully when quorum does not met Problem: replace-brick command on a setup where quorum does not met executing successfully. Fix: With the fix glusterd is validating whether server is in quorum or not during replace-brick staging Change-Id: I8017154bb62bdcc6c6490e720ecfe9cde090c161 BUG: 1483058 Signed-off-by: Gaurav Yadav <gyadav> Reviewed-on: https://review.gluster.org/18068 Smoke: Gluster Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Atin Mukherjee <amukherj>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.13.0, please open a new bug report. glusterfs-3.13.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2017-December/000087.html [2] https://www.gluster.org/pipermail/gluster-users/