Bug 1637564
Summary: | Customer reports regression of BZ 1441055 with NFS-Ganesha in gluster 3.8.4-54 | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Andrew Robinson <anrobins> |
Component: | common-ha | Assignee: | Kaleb KEITHLEY <kkeithle> |
Status: | CLOSED ERRATA | QA Contact: | Jilju Joy <jijoy> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhgs-3.3 | CC: | anrobins, bkunal, dang, ffilz, grajoria, jthottan, kkeithle, mbenjamin, nchilaka, rhs-bugs, sankarshan, sheggodu, skoduri, srmukher, storage-qa-internal, vdas |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | RHGS 3.4.z Batch Update 3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.12.2-33 | Doc Type: | Bug Fix |
Doc Text: |
Earlier, a race condition between `pcs cluster setup ...` and `systemctl enable pacemaker` sometimes left Pacemaker disabled. As a result, Pacemaker failed to start on one or more nodes after reboot. With this release, the '--enable' option has been added to the `pcs cluster setup ...` command to enable and start Pacemaker automatically after reboot.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-02-04 07:41:25 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: | |||
Bug Blocks: | 1649191 |
Description
Andrew Robinson
2018-10-09 13:40:41 UTC
*** Bug 1641673 has been marked as a duplicate of this bug. *** https://code.engineering.redhat.com/gerrit/154376 Since https://bugzilla.redhat.com/show_bug.cgi?id=1641673 has already been closed I am clearing the Needinfo. Verified this with below scenarios. 1. Configure ganesha on fresh setup 1.1. with pacemaker already enabled on all nodes. 1.2. with pacemaker disabled on all nodes. 1.3. with pacemaker already enabled only on few nodes. 2. Disable existing ganesha cluster. Enable ganesha cluster 2.1. with pacemaker already enabled on all nodes. 2.2. with pacemaker disabled on all nodes. 2.3. with pacemaker already enabled only on few nodes. 2.3.1. Ganesha enable from node where pacemaker is enabled. 2.3.2. Ganesha enable from node where pacemaker is disabled. 3. Disable pacemaker on existing ganesha nodes --> disable ganesha cluster --> enable ganesha. 4. Disable pacemaker on existing ganesha nodes --> disable ganesha cluster --> enable pacemaker on nodes --> enable ganesha. Result: pacemaker is 'enabled' after setting up ganesha. Based on the observations, marking this bug as verified. The doc text has been updated. Kindly review the technical accuracy. 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/RHBA-2019:0263 updated Doc Text. |