Bug 1482844

Summary: glusterd fails to start
Product: [Community] GlusterFS Reporter: Gaurav Yadav <gyadav>
Component: glusterdAssignee: Gaurav Yadav <gyadav>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 3.12CC: amukherj, bmekala, olim, rhs-bugs, rmetrich, sbairagy, storage-qa-internal, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1449867 Environment:
Last Closed: 2017-08-21 04:54:24 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: 1449867, 1472267, 1482835, 1482857    
Bug Blocks:    

Description Gaurav Yadav 2017-08-18 08:27:39 UTC
+++ This bug was initially created as a clone of Bug #1449867 +++

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 Atin Mukherjee 2017-08-21 04:54:24 UTC

*** This bug has been marked as a duplicate of bug 1482835 ***