Bug 1233246

Summary: nfs-ganesha: add node fails to add a new node to the cluster
Product: [Community] GlusterFS Reporter: Meghana <mmadhusu>
Component: common-haAssignee: Kaleb KEITHLEY <kkeithle>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: unspecified    
Version: mainlineCC: kkeithle, nlevinki, rcyriac, saujain, skoduri, storage-qa-internal, vagarwal
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.8rc2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1228626
: 1234216 (view as bug list) Environment:
Last Closed: 2016-06-16 13:14:28 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: 1228626    
Bug Blocks: 1202842, 1234216    

Comment 1 Anand Avati 2015-06-18 14:34:16 UTC
REVIEW: http://review.gluster.org/11316 (common-ha : Fixing add node operation) posted (#1) for review on master by Meghana M (mmadhusu)

Comment 2 Anand Avati 2015-06-19 07:29:06 UTC
REVIEW: http://review.gluster.org/11316 (common-ha : Fixing add node operation) posted (#2) for review on master by Meghana M (mmadhusu)

Comment 3 Anand Avati 2015-06-19 10:01:32 UTC
REVIEW: http://review.gluster.org/11316 (common-ha : Fixing add node operation) posted (#4) for review on master by Meghana M (mmadhusu)

Comment 4 Anand Avati 2015-06-19 13:52:38 UTC
COMMIT: http://review.gluster.org/11316 committed in master by Kaleb KEITHLEY (kkeithle) 
------
commit e19552c8cc42a3c80aaf43e70f6e29011ad23516
Author: Meghana M <mmadhusu>
Date:   Thu Jun 18 06:39:41 2015 +0530

    common-ha : Fixing add node operation
    
    Resource create for the added node referenced a variable
    new_node that was never passed. This led to a wrong schema
    type in the cib file and hence the added node always ended
    up in failed state. And also, resources were wrongly
    created twice and led to more errors. I have fixed the variable
    name and deleted the repetitive invocation of the recreate-resource
    function.
    
    The new node has to be added to the existing ganesha-ha config
    file for correct behaviour during subsequent add-node operations.
    This edited file has to be copied to all the other cluster nodes.
    I have added a fix for this as well.
    
    Change-Id: Ie55138e2657d22298d89db1c08f2e17930686bd6
    BUG: 1233246
    Signed-off-by: Meghana M <mmadhusu>
    Reviewed-on: http://review.gluster.org/11316
    Reviewed-by: Niels de Vos <ndevos>
    Reviewed-by: soumya k <skoduri>
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>

Comment 7 Nagaprasad Sathyanarayana 2015-10-25 14:41:49 UTC
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.

Comment 8 Niels de Vos 2016-06-16 13:14:28 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.8.0, please open a new bug report.

glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user