Bug 1405576 - [GANESHA] failed to create directory of hostname of new node in var/lib/nfs/ganesha/ in already existing cluster nodes
Summary: [GANESHA] failed to create directory of hostname of new node in var/lib/nfs/g...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: common-ha
Version: 3.9
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
Assignee: Kaleb KEITHLEY
QA Contact:
URL:
Whiteboard:
Depends On: 1400599 1400613
Blocks: 1405577
TreeView+ depends on / blocked
 
Reported: 2016-12-16 18:16 UTC by Kaleb KEITHLEY
Modified: 2017-03-08 10:23 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.9.1
Clone Of: 1400613
: 1405577 (view as bug list)
Environment:
Last Closed: 2017-02-21 11:22:04 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Worker Ant 2016-12-16 18:23:38 UTC
REVIEW: http://review.gluster.org/16170 (common-ha: add node create new node dirs in shared storage) posted (#1) for review on release-3.9 by Kaleb KEITHLEY (kkeithle)

Comment 2 Worker Ant 2016-12-18 12:44:05 UTC
COMMIT: http://review.gluster.org/16170 committed in release-3.9 by Kaleb KEITHLEY (kkeithle) 
------
commit 88a096ed0952ee2ae8e8684c99aadd2c1f3f9e5e
Author: Kaleb S. KEITHLEY <kkeithle>
Date:   Fri Dec 16 13:21:03 2016 -0500

    common-ha: add node create new node dirs in shared storage
    
    When adding a node to the ganesha HA cluster, create the directory
    tree in shared storage for the added node and create sets of symlinks
    to match what is/was created for the other nodes.  I.e. in a four
    node cluster the new node needs a set of links to the four existing
    nodes:
     /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e1 -> e1
     /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e2 -> e2
     /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e3 -> e3
     /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e4 -> e4
    and all the existing nodes need links added for the new node:
     /run/gluster/shared/nfs-ganesha/$e1/nfs/{ganesha,statd}/$new -> new
     /run/gluster/shared/nfs-ganesha/$e2/nfs/{ganesha,statd}/$new -> new
     /run/gluster/shared/nfs-ganesha/$e3/nfs/{ganesha,statd}/$new -> new
     /run/gluster/shared/nfs-ganesha/$e5/nfs/{ganesha,statd}/$new -> new
    
    Likewise when deleting, remove the dir and symlinks.
    
    master BZ: 1400613
    
    Change-Id: Id2f78f70946f29c3503e1e6db141b66cb431e0ea
    BUG: 1405576
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle>
    Reviewed-on: http://review.gluster.org/16170
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 3 Worker Ant 2016-12-20 16:00:23 UTC
REVIEW: http://review.gluster.org/16217 (common-ha: add node create new node dirs in shared storage) posted (#1) for review on release-3.9 by Kaleb KEITHLEY (kkeithle)

Comment 4 Worker Ant 2016-12-21 18:06:30 UTC
REVIEW: http://review.gluster.org/16217 (common-ha: add node create new node dirs in shared storage) posted (#2) for review on release-3.9 by Kaleb KEITHLEY (kkeithle)

Comment 5 Worker Ant 2016-12-22 14:20:26 UTC
COMMIT: http://review.gluster.org/16217 committed in release-3.9 by Kaleb KEITHLEY (kkeithle) 
------
commit 6e8ac80b29b37c215f18f646ee4a3f3fffccb3bc
Author: Kaleb S. KEITHLEY <kkeithle>
Date:   Tue Dec 20 10:56:35 2016 -0500

    common-ha: add node create new node dirs in shared storage
    
    When adding a node to the ganesha HA cluster, create the directory
    tree in shared storage for the added node and create sets of symlinks
    to match what is/was created for the other nodes.  I.e. in a four
    node cluster the new node needs a set of links to the four existing
    nodes:
     /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e1 -> e1
     /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e2 -> e2
     /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e3 -> e3
     /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e4 -> e4
    and all the existing nodes need links added for the new node:
     /run/gluster/shared/nfs-ganesha/$e1/nfs/{ganesha,statd}/$new -> new
     /run/gluster/shared/nfs-ganesha/$e2/nfs/{ganesha,statd}/$new -> new
     /run/gluster/shared/nfs-ganesha/$e3/nfs/{ganesha,statd}/$new -> new
     /run/gluster/shared/nfs-ganesha/$e5/nfs/{ganesha,statd}/$new -> new
    
    Likewise when deleting, remove the dir and symlinks.
    
    original change http://review.gluster.org/16036
    original change release-3.9 http://review.gluster.org/16170
    master change http://review.gluster.org/16216
    master BZ 1400613
    
    Change-Id: I52839046745728d06ab5a07f38081c032093bff6
    BUG: 1405576
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle>
    Reviewed-on: http://review.gluster.org/16217
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 6 Kaushal 2017-03-08 10:22:32 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/

Comment 7 Kaushal 2017-03-08 10:23:21 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/


Note You need to log in before you can comment on or make changes to this bug.