Bug 1403130

Summary:	[GANESHA] Adding a node to cluster failed to allocate resource-agents to new node.
Product:	[Community] GlusterFS	Reporter:	Soumya Koduri <skoduri>
Component:	common-ha	Assignee:	Soumya Koduri <skoduri>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	urgent
Version:	mainline	CC:	aloganat, amukherj, bugs, jthottan, kkeithle, msaini, ndevos, rcyriac, rhs-bugs, sbhaloth, skoduri, storage-qa-internal
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-3.10.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1400068
Clones:	1404133 (view as bug list)		Environment:
Last Closed:	2017-03-06 17:39:10 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:	1400068, 1404133

Comment 1 Soumya Koduri 2016-12-09 06:54:09 UTC

Description of problem:

Adding a node to nfs-ganesha cluster does not create portblock resource agents. Also this bug addresses cleaning up those resources as part of delete-node and adjusting quorum-policy accordingly.

Comment 2 Worker Ant 2016-12-09 06:55:30 UTC

REVIEW: http://review.gluster.org/16089 (common-ha: Create portblock RA as part of add/delete-node) posted (#1) for review on master by soumya k (skoduri)

Comment 3 Worker Ant 2016-12-13 00:41:53 UTC

COMMIT: http://review.gluster.org/16089 committed in master by Kaleb KEITHLEY (kkeithle) 
------
commit 885ecce6e2df6464b388f42c91211ed31e17654d
Author: Soumya Koduri <skoduri>
Date:   Fri Dec 9 12:18:28 2016 +0530

    common-ha: Create portblock RA as part of add/delete-node
    
    When a node is added to or deleted from existing nfs-ganesha cluster,
    we need to create or cleanup portblock RA as well. This patch is
    to address the same. Also we need to adjust the quorum-policy with
    increase/decrease in the number of nodes in the cluster.
    
    Change-Id: I31a896715b9b7fc931009723d1570bf7aa4da9b6
    BUG: 1403130
    Signed-off-by: Soumya Koduri <skoduri>
    Reviewed-on: http://review.gluster.org/16089
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: jiffin tony Thottan <jthottan>
    Reviewed-by: Kaleb KEITHLEY <kkeithle>

Comment 4 Shyamsundar 2017-03-06 17:39:10 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.10.0, please open a new bug report.

glusterfs-3.10.0 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-February/030119.html
[2] https://www.gluster.org/pipermail/gluster-users/