[Bugs] [Bug 1482835] New: glusterd fails to start

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1482835

            Bug ID: 1482835
           Summary: glusterd fails to start
           Product: GlusterFS
           Version: 3.12
         Component: glusterd
          Keywords: Triaged
          Severity: high
          Priority: high
          Assignee: bugs at gluster.org
          Reporter: amukherj at redhat.com
                CC: amukherj at redhat.com, bmekala at redhat.com,
                    bugs at gluster.org, gyadav at redhat.com, olim at redhat.com,
                    rhs-bugs at redhat.com, rmetrich at redhat.com,
                    sbairagy at redhat.com, storage-qa-internal at redhat.com,
                    vbellur at redhat.com
        Depends On: 1472267
            Blocks: 1449867



+++ This bug was initially created as a clone of Bug #1472267 +++

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".

--- Additional comment from Atin Mukherjee on 2017-07-24 00:50:08 EDT ---

patch : https://review.gluster.org/#/c/17813/

--- Additional comment from Worker Ant on 2017-07-26 07:08:54 EDT ---

REVIEW: https://review.gluster.org/17813 (glusterd : glusterd fails to start
when  peer's network interface is down) posted (#4) for review on master by
Gaurav Yadav (gyadav at redhat.com)

--- Additional comment from Worker Ant on 2017-07-26 13:45:29 EDT ---

REVIEW: https://review.gluster.org/17813 (glusterd : glusterd fails to start
when  peer's network interface is down) posted (#5) for review on master by
Gaurav Yadav (gyadav at redhat.com)

--- Additional comment from Worker Ant on 2017-07-28 00:47:29 EDT ---

COMMIT: https://review.gluster.org/17813 committed in master by Atin Mukherjee
(amukherj at redhat.com) 
------
commit 1477fa442a733d7b1a5ea74884cac8f29fbe7e6a
Author: Gaurav Yadav <gyadav at redhat.com>
Date:   Tue Jul 18 16:23:18 2017 +0530

    glusterd : glusterd fails to start when  peer's network interface is down

    Problem:
    glusterd fails to start on nodes where glusterd tries to come up even
    before network is up.

    Fix:
    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.

    Change-Id: Icfa7b2652417135530479d0aa4e2a82b0476f710
    BUG: 1472267
    Signed-off-by: Gaurav Yadav <gyadav at redhat.com>
    Reviewed-on: https://review.gluster.org/17813
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai at redhat.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1472267
[Bug 1472267] glusterd fails to start
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.