Bug 1418999
| Summary: | [GDEPLOY+GANESHA] Gdeploy fails to delete a node from ganesha cluster | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Manisha Saini <msaini> |
| Component: | gdeploy | Assignee: | Sachidananda Urs <surs> |
| Status: | CLOSED ERRATA | QA Contact: | Manisha Saini <msaini> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | rhgs-3.2 | CC: | amukherj, asrivast, bmohanra, msaini, rcyriac, rhinduja, rhs-bugs, smohan, storage-qa-internal |
| Target Milestone: | --- | ||
| Target Release: | RHGS 3.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | gdeploy-2.0.1-2 | Doc Type: | Bug Fix |
| Doc Text: |
Deletion of a node from NFS Ganesha would fail, as the playbook `hosts' section was not pointed to the correct node.
Workaround:
The node has to be deleted using the script: /usr/libexec/ganesha/ganesha-ha.sh
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-09-21 04:49:50 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: | 1417147 | ||
|
Description
Manisha Saini
2017-02-03 12:01:13 UTC
Atin, To delete a node from the cluster, we have to execute the following command on any of the nodes in the existing NFS-Ganesha cluster: /usr/libexec/ganesha/ganesha-ha.sh --delete <HA_CONF_DIR> <HOSTNAME> where <HA_CONF_DIR> is /var/run/gluster/shared_storage/nfs_ganesha <HOSTNAME> hostname of the node which we want to delete eg- /usr/libexec/ganesha/ganesha-ha.sh --delete /var/run/gluster/shared_storage/nfs-ganesha/ dhcp46-232.lab.eng.blr.redhat.com @Rejy - can you please take out the blocker flag? The doc text is edited for the release notes. Commit: https://github.com/gluster/gdeploy/commit/ba937643bed3222f102fdc9e160e3668877a5321#diff-8c51d9452d7dc1259c9d2975d21f0ea7 Fixes the issue. Verified this bug on [root@dhcp47-132 home]# rpm -qa | grep gdeploy gdeploy-2.0.2-2.el7rhgs.noarch Delete node config file - # cat delete_node.conf [hosts] dhcp47-147.lab.eng.blr.redhat.com dhcp47-141.lab.eng.blr.redhat.com dhcp47-144.lab.eng.blr.redhat.com dhcp47-139.lab.eng.blr.redhat.com dhcp47-132.lab.eng.blr.redhat.com [nfs-ganesha] action=delete-node nodes=dhcp47-132.lab.eng.blr.redhat.com As the issue is no more observed,hence moving this bug to Verified state 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-2017:2777 |