Description of problem: It would be good if /usr/libexec/ganesha/ganesha-ha.sh --status , checks the following. * Whether nfs-ganesha service is running on all nfs-ganesha cluster nodes. * Whether pacemaker, pcs, corosync is running on all nfs-ganesha cluster nodes. * whether pcs status shows all the hostnames in which nfs-ganesha cluster is configured and its Virtual IP's respectively. * As overall status , whether nfs-ganesha servers are in HA, or all the nodes are HEALTHY. Currently, if ganesha is configured in 4 nodes, and in one node if pacemaker service is not enabled, then in the other node, it shows the status of only the nodes which are online. Version-Release number of selected component (if applicable): nfs-ganesha-gluster-2.4.1-1.el7rhgs.x86_64 How reproducible: Always Steps to Reproduce: 1. Setup 4 node nfs-ganesha cluster. 2. Stop pacemaker in one of the node. 3. Run /usr/libexec/ganesha/ganesha-ha.sh --status in other node. Actual results: It shows the status of only the nodes which are online Expected results: It should check whether for all services used in nfs-ganesha are running and gives the status. Additional info: Node in which pacemaker not running. -------------------------------------- [root@dhcp46-111 ~]# service pacemaker status Redirecting to /bin/systemctl status pacemaker.service ● pacemaker.service - Pacemaker High Availability Cluster Manager Loaded: loaded (/usr/lib/systemd/system/pacemaker.service; disabled; vendor preset: disabled) Active: inactive (dead) Docs: man:pacemakerd http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Pacemaker_Explained/index.html /usr/libexec/ganesha/ganesha-ha.sh --status in other node: ---------------------------------------------------------- [root@dhcp46-115 ~]# /usr/libexec/ganesha/ganesha-ha.sh --status Online: [ dhcp46-115.lab.eng.blr.redhat.com dhcp46-124.lab.eng.blr.redhat.com dhcp46-139.lab.eng.blr.redhat.com ] dhcp46-115.lab.eng.blr.redhat.com-cluster_ip-1 dhcp46-115.lab.eng.blr.redhat.com dhcp46-139.lab.eng.blr.redhat.com-cluster_ip-1 dhcp46-139.lab.eng.blr.redhat.com dhcp46-124.lab.eng.blr.redhat.com-cluster_ip-1 dhcp46-124.lab.eng.blr.redhat.com
We can certainly work on fixing --status reliable for gdeploy. The rest of is way too ambitious in the time remaining, and we're already past feature freeze.