Bug 1310632
Summary: | Newly created volume start, starting the bricks when server quorum not met | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Gaurav Kumar Garg <ggarg> |
Component: | glusterd | Assignee: | Gaurav Kumar Garg <ggarg> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.7.0 | CC: | amukherj, bsrirama, bugs, ggarg, rcyriac, smohan, storage-qa-internal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.7.9 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1308402 | Environment: | |
Last Closed: | 2016-04-19 07:23:31 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: | 1308402 | ||
Bug Blocks: |
Comment 1
Vijay Bellur
2016-02-22 12:26:40 UTC
REVIEW: http://review.gluster.org/13484 (glusterd: volume should not start when server quorum is not met) posted (#2) for review on release-3.7 by Gaurav Kumar Garg (ggarg) *** Bug 1310630 has been marked as a duplicate of this bug. *** *** Bug 1310631 has been marked as a duplicate of this bug. *** *** Bug 1310630 has been marked as a duplicate of this bug. *** COMMIT: http://review.gluster.org/13484 committed in release-3.7 by Atin Mukherjee (amukherj) ------ commit 794e3e8a7448219e0de303e57b0104896b18746e Author: Gaurav Kumar Garg <garg.gaurav52> Date: Mon Feb 22 17:53:53 2016 +0530 glusterd: volume should not start when server quorum is not met This patch is backport of: http://review.gluster.org/#/c/13442 Currently when server quorum is not met then upon executing # gluster volume start [force] command its starting the volume. With this patch if server side quorum is not met then it will prevent starting of the volume. >> Change-Id: I39734b2dcf8e90c3c68bf2762d8350aecc82cc38 >> BUG: 1308402 >> Signed-off-by: Gaurav Kumar Garg <ggarg> >> Reviewed-on: http://review.gluster.org/13442 >> Smoke: Gluster Build System <jenkins.com> >> Reviewed-by: Atin Mukherjee <amukherj> >> CentOS-regression: Gluster Build System <jenkins.com> >> NetBSD-regression: NetBSD Build System <jenkins.org> Change-Id: Iacb65823fb091e4ac250e436d1cb10103bc24921 BUG: 1310632 Signed-off-by: Gaurav Kumar Garg <ggarg> Reviewed-on: http://review.gluster.org/13484 Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> 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.7.9, please open a new bug report. glusterfs-3.7.9 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] https://www.gluster.org/pipermail/gluster-users/2016-March/025922.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |