Bug 1394882
Summary: | Failed to enable nfs-ganesha after disabling nfs-ganesha cluster | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Kaleb KEITHLEY <kkeithle> | |
Component: | common-ha | Assignee: | Kaleb KEITHLEY <kkeithle> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 3.9 | CC: | aloganat, amukherj, bugs, jthottan, kkeithle, ndevos, rhinduja, rhs-bugs, skoduri, storage-qa-internal | |
Target Milestone: | --- | Keywords: | Triaged | |
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.9.1 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1394881 | |||
: | 1394883 (view as bug list) | Environment: | ||
Last Closed: | 2017-01-24 11:38:49 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: | 1392895, 1394881 | |||
Bug Blocks: | 1394883 |
Description
Kaleb KEITHLEY
2016-11-14 16:00:55 UTC
REVIEW: http://review.gluster.org/15844 (common-ha: remove /etc/corosync/corosync.conf in teardown/cleanup) posted (#1) for review on release-3.9 by Kaleb KEITHLEY (kkeithle) REVIEW: http://review.gluster.org/15844 (common-ha: remove /etc/corosync/corosync.conf in teardown/cleanup) posted (#2) for review on release-3.9 by Kaleb KEITHLEY (kkeithle) REVIEW: http://review.gluster.org/15844 (common-ha: remove /etc/corosync/corosync.conf in teardown/cleanup) posted (#3) for review on release-3.9 by Kaleb KEITHLEY (kkeithle) COMMIT: http://review.gluster.org/15844 committed in release-3.9 by Kaleb KEITHLEY (kkeithle) ------ commit b13c2af3e970990537e66d00a107a61b8c3fa643 Author: Kaleb S. KEITHLEY <kkeithle> Date: Mon Nov 14 11:21:49 2016 -0500 common-ha: remove /etc/corosync/corosync.conf in teardown/cleanup In newer versions of corosync we observe that after tearing down an existing HA cluster, when trying to set up a new cluster, `pcs cluster start --all` will fail if corosync believes the nodes are already in the cluster based on the presence of, and the contents of /etc/corosync/corosync.conf So we summarily delete it. (An alternative/work-around is to use `pcs cluster start --force --all`) Change-Id: I225f4e35e3b605e860ec4f9537c40ed94ac68625 BUG: 1394882 Signed-off-by: Kaleb S. KEITHLEY <kkeithle> Reviewed-on: http://review.gluster.org/15844 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: soumya k <skoduri> 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.9.1, please open a new bug report. glusterfs-3.9.1 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/gluster-users/2017-January/029725.html [2] https://www.gluster.org/pipermail/gluster-users/ |