Description of problem: Bug 1441055 - pacemaker service is disabled after creating nfs-ganesha cluster. Customer report regression of this BZ when setting up NFS-Ganesha in gluster 3.8.4-54 Version-Release number of selected component (if applicable): RHGS 3.3.1 gluster 3.8.4-54 How reproducible: Configure NFS-Ganesha on a gluster cluster on which the pacemaker service has been previously enabled. Steps to Reproduce: 1. Enable pacemaker on gluster cluster prior to configuring NFS-Ganesha 2. Configure NFS-Ganesha 3. See pacemaker disabled Actual results: Pacemaker service disabled Expected results: Pacemaker server not disabled Additional info:
*** 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.