Bug 1395649

Summary:	ganesha-ha.conf --status should validate if the VIPs are assigned to right nodes
Product:	[Community] GlusterFS	Reporter:	Kaleb KEITHLEY <kkeithle>
Component:	common-ha	Assignee:	Kaleb KEITHLEY <kkeithle>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.9	CC:	aloganat, amukherj, asrivast, bugs, jthottan, kkeithle, mzywusko, rhinduja, rhs-bugs, skoduri, storage-qa-internal
Target Milestone:	---	Keywords:	Reopened, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.9.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1395648
Clones:	1395652 (view as bug list)		Environment:
Last Closed:	2017-01-24 11:36:56 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:	1395539, 1395648
Bug Blocks:	1364410, 1393966, 1394815, 1395652

Comment 1 Worker Ant 2016-12-01 13:11:40 UTC

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)

Comment 2 Worker Ant 2016-12-01 20:40:28 UTC

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>

Comment 3 Kaushal 2017-03-08 10:20:37 UTC

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/