Bug 1482857 - glusterd fails to start
Summary: glusterd fails to start
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Gaurav Yadav
QA Contact:
Depends On: 1449867 1472267 1482835
Blocks: 1482844
TreeView+ depends on / blocked
Reported: 2017-08-18 08:39 UTC by Gaurav Yadav
Modified: 2017-10-06 17:10 UTC (History)
8 users (show)

Fixed In Version: glusterfs-3.10.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1449867
Last Closed: 2017-10-06 17:10:52 UTC
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:

Attachments (Terms of Use)

Description Gaurav Yadav 2017-08-18 08:39:50 UTC
Consider the case where the storage node is stopped and on restart the storage node gets a new ip_address or hostname or one of the peer's network interface is not up. In this case glusterd is not starting. 

glusterd logs gives error as "glusterd resolve brick failed in restore".

Comment 1 Worker Ant 2017-08-18 11:33:44 UTC
REVIEW: https://review.gluster.org/18063 (glusterd : glusterd fails to start when  peer's network interface is down) posted (#2) for review on release-3.10 by Gaurav Yadav (gyadav@redhat.com)

Comment 2 Worker Ant 2017-09-17 12:47:44 UTC
COMMIT: https://review.gluster.org/18063 committed in release-3.10 by Shyamsundar Ranganathan (srangana@redhat.com) 
commit 78a4218c4838e4844e4ea130a1740359e459a622
Author: Gaurav Yadav <gyadav@redhat.com>
Date:   Tue Jul 18 16:23:18 2017 +0530

    glusterd : glusterd fails to start when  peer's network interface is down
    glusterd fails to start on nodes where glusterd tries to come up even
    before network is up.
    On startup glusterd tries to resolve brick path which is based on
    hostname/ip, but in the above scenario when network interface is not
    up, glusterd is not able to resolve the brick path using ip_address or
    hostname With this fix glusterd will use UUID to resolve brick path.
    >Reviewed-on: https://review.gluster.org/17813
    >Smoke: Gluster Build System <jenkins@build.gluster.org>
    >Reviewed-by: Prashanth Pai <ppai@redhat.com>
    >CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    >Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Change-Id: Icfa7b2652417135530479d0aa4e2a82b0476f710
    BUG: 1482857
    Signed-off-by: Gaurav Yadav <gyadav@redhat.com>
    Reviewed-on: https://review.gluster.org/18063
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

Comment 3 Shyamsundar 2017-10-06 17:10:52 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.6, please open a new bug report.

glusterfs-3.10.6 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/announce/2017-October/000084.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.