REVIEW: http://review.gluster.org/15991 (common-ha: add cluster HA status to --status output for gdeploy) posted (#1) for review on release-3.9 by Kaleb KEITHLEY (kkeithle)
COMMIT: http://review.gluster.org/15991 committed in release-3.9 by Kaleb KEITHLEY (kkeithle) ------ commit 5fbab30470004280627777c176326d358d23833c Author: Kaleb S. KEITHLEY <kkeithle> Date: Fri Nov 18 13:07:50 2016 -0500 common-ha: add cluster HA status to --status output for gdeploy gdeploy desires a one-liner "health" assessment. If all the VIP and port block/unblock RAs are located on their prefered nodes and 'Started', then the cluster is deemed to be good (healthy). N.B. status originally only checked the "online" nodes obtained from `pcs status` but we really want to consider all the configured nodes, whether they are online or not. Also one `pcs status` is enough. master bug 1395648 master http://review.gluster.org/15882 Change-Id: Id0e0380b6982e23763edeb0488843b5363e370b8 BUG: 1395649 Signed-off-by: Kaleb S. KEITHLEY <kkeithle> Reviewed-by: Arthy Loganathan <aloganat> Reviewed-by: soumya k <skoduri> Reviewed-on: http://review.gluster.org/15991 Tested-by: soumya k <skoduri> Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.9.1, please open a new bug report. glusterfs-3.9.1 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/gluster-users/2017-January/029725.html [2] https://www.gluster.org/pipermail/gluster-users/