Description of problem: Gdeploy fails to delete a node from existing ganesha cluster Version-Release number of selected component (if applicable): # rpm -qa | grep gdeploy gdeploy-2.0.1-9.el7rhgs.noarch How reproducible: Consistently Steps to Reproduce: 1.Create 5 Node ganesha cluster.Enable ganesha on it 2.From gdeploy delete 1 node from 5 node ganesha cluster # cat delete_node.conf [hosts] dhcp46-87.lab.eng.blr.redhat.com dhcp46-96.lab.eng.blr.redhat.com dhcp46-112.lab.eng.blr.redhat.com dhcp47-41.lab.eng.blr.redhat.com dhcp46-38.lab.eng.blr.redhat.com [nfs-ganesha] action=delete-node nodes=dhcp46-38.lab.eng.blr.redhat.com ============= # gdeploy -c delete_node.conf PLAY RECAP ********************************************************************* ============ Actual results: It fails to delete the node from ganesha cluster Expected results: Gdeploy should be able to delete the node from ganesha cluster Additional info:
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