[Bugs] [Bug 1394883] New: Failed to enable nfs-ganesha after disabling nfs-ganesha cluster

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1394883

            Bug ID: 1394883
           Summary: Failed to enable nfs-ganesha after disabling
                    nfs-ganesha cluster
           Product: GlusterFS
           Version: 3.8
         Component: common-ha
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: kkeithle at redhat.com
                CC: aloganat at redhat.com, bugs at gluster.org,
                    jthottan at redhat.com, kkeithle at redhat.com,
                    ndevos at redhat.com, rhinduja at redhat.com,
                    rhs-bugs at redhat.com, skoduri at redhat.com,
                    storage-qa-internal at redhat.com
        Depends On: 1392895, 1394881, 1394882
            Blocks: 1351528



+++ This bug was initially created as a clone of Bug #1394882 +++

+++ This bug was initially created as a clone of Bug #1394881 +++

+++ This bug was initially created as a clone of Bug #1392895 +++

Description of problem:
Failed to enable nfs-ganesha after disabling nfs-ganesha cluster

Version-Release number of selected component (if applicable):
nfs-ganesha-gluster-2.4.1-1.el7rhgs.x86_64
glusterfs-ganesha-3.8.4-3.el7rhgs.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Create nfs-ganesha cluster.
2. Disable nfs ganesha.
3. Try to enable nfs-ganesha again.


Actual results:
Failed to enable nfs-ganesha after disabling nfs-ganesha cluster

Expected results:
nfs-ganesha should be enabled.

Additional info:

Command line log snippet:

[root at dhcp46-111 ~]# gluster nfs-ganesha disable
Disabling NFS-Ganesha will tear down entire ganesha cluster across the trusted
pool. Do you still want to continue?
 (y/n) y
This will take a few minutes to complete. Please wait ..
nfs-ganesha : success 
[root at dhcp46-111 ~]# 
[root at dhcp46-111 ~]# 
[root at dhcp46-111 ~]# gluster nfs-ganesha enable
Enabling NFS-Ganesha requires Gluster-NFS to be disabled across the trusted
pool. Do you still want to continue?
 (y/n) y
This will take a few minutes to complete. Please wait ..
nfs-ganesha: failed: Failed to set up HA config for NFS-Ganesha. Please check
the log file for details


/var/log/messages snippet:

Nov  8 17:49:30 dhcp46-111 logger: setting up cluster G1478590172.02 with the
following dhcp46-111.lab.eng.blr.redhat.com dhcp46-115.lab.eng.blr.redhat.com
dhcp46-139.lab.eng.blr.redhat.com dhcp46-124.lab.eng.blr.redhat.com
Nov  8 17:49:35 dhcp46-111 logger: pcs cluster setup --name G1478590172.02
dhcp46-111.lab.eng.blr.redhat.com dhcp46-115.lab.eng.blr.redhat.com
dhcp46-139.lab.eng.blr.redhat.com dhcp46-124.lab.eng.blr.redhat.com failed

--- Additional comment from Red Hat Bugzilla Rules Engine on 2016-11-08
07:31:09 EST ---

This bug is automatically being proposed for the current release of Red Hat
Gluster Storage 3 under active development, by setting the release flag
'rhgs‑3.2.0' to '?'. 

If this bug should be proposed for a different release, please manually change
the proposed release flag.

--- Additional comment from Arthy Loganathan on 2016-11-08 07:32 EST ---



--- Additional comment from Soumya Koduri on 2016-11-08 07:47:45 EST ---

Could you please provide access to your machine. Last night when I looked at
it, it complained about other nodes being already part of the cluster. Once we
remove /etc/corosync/corosync.conf file manually, the setup succeeds. 

There might have been some changes in the latest RHEL 7.3 pacemaker/corosync
packages as this was not the case in the previous version. Could you please
confirm that?

--- Additional comment from Arthy Loganathan on 2016-11-09 00:46:08 EST ---

Please access the machine with below details,
IP : 10.70.46.111.
Credentials : root/redhat

--- Additional comment from Red Hat Bugzilla Rules Engine on 2016-11-14
05:07:24 EST ---

This bug is automatically being provided 'pm_ack+' for the release flag
'rhgs‑3.2.0', the current release of Red Hat Gluster Storage 3 under active
development, having been appropriately marked for the release, and having been
provided ACK from Development and QE

If the 'blocker' flag had been proposed/set on this BZ, it has now been unset,
since the 'blocker' flag is not valid for the current phase of RHGS 3.2.0
development

--- Additional comment from Red Hat Bugzilla Rules Engine on 2016-11-14
06:53:12 EST ---

Since this bug has been approved for the RHGS 3.2.0 release of Red Hat Gluster
Storage 3, through release flag 'rhgs-3.2.0+', and through the Internal
Whiteboard entry of '3.2.0', the Target Release is being automatically set to
'RHGS 3.2.0'


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1392895
[Bug 1392895] Failed to enable nfs-ganesha after disabling nfs-ganesha
cluster
https://bugzilla.redhat.com/show_bug.cgi?id=1394881
[Bug 1394881] Failed to enable nfs-ganesha after disabling nfs-ganesha
cluster
https://bugzilla.redhat.com/show_bug.cgi?id=1394882
[Bug 1394882] Failed to enable nfs-ganesha after disabling nfs-ganesha
cluster
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.