Bug 1472267
Summary: | glusterd fails to start | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Gaurav Yadav <gyadav> | |
Component: | glusterd | Assignee: | Gaurav Yadav <gyadav> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | mainline | CC: | amukherj, bmekala, olim, rhs-bugs, rmetrich, sbairagy, storage-qa-internal, vbellur | |
Target Milestone: | --- | Keywords: | Triaged | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.13.0 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1449867 | |||
: | 1482835 (view as bug list) | Environment: | ||
Last Closed: | 2017-12-08 17:34:10 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: | ||||
Bug Blocks: | 1449867, 1482835, 1482844, 1482857 |
Description
Gaurav Yadav
2017-07-18 10:29:15 UTC
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) 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) COMMIT: https://review.gluster.org/17813 committed in master by Atin Mukherjee (amukherj) ------ commit 1477fa442a733d7b1a5ea74884cac8f29fbe7e6a Author: Gaurav Yadav <gyadav> 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> Reviewed-on: https://review.gluster.org/17813 Smoke: Gluster Build System <jenkins.org> Reviewed-by: Prashanth Pai <ppai> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Atin Mukherjee <amukherj> REVIEW: https://review.gluster.org/18063 (glusterd : glusterd fails to start when peer's network interface is down) posted (#1) for review on release-3.10 by Gaurav Yadav (gyadav) 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.13.0, please open a new bug report. glusterfs-3.13.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://lists.gluster.org/pipermail/announce/2017-December/000087.html [2] https://www.gluster.org/pipermail/gluster-users/ |