Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1449867 - [GSS] glusterd fails to start
[GSS] glusterd fails to start
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd (Show other bugs)
3.2
Unspecified Unspecified
high Severity high
: ---
: RHGS 3.4.0
Assigned To: Atin Mukherjee
Bala Konda Reddy M
rebase
: ZStream
Depends On: 1472267 1482835
Blocks: RHGS-3.4-GSS-proposed-tracker 1482844 1482857 1503135
  Show dependency treegraph
 
Reported: 2017-05-10 22:19 EDT by Oonkwee Lim_
Modified: 2018-09-17 09:19 EDT (History)
10 users (show)

See Also:
Fixed In Version: glusterfs-3.12.2-1
Doc Type: Bug Fix
Doc Text:
Earlier in case of a node reboot, if the network interface takes time to come up before glusterd service, glusterd used to fail to resolve the brick addresses which belong to different peers resulting glusterd service to fail to come up. With this fix, even though the network interface is in process of coming up, glusterd will not fail to come up.
Story Points: ---
Clone Of:
: 1472267 1482844 1482857 (view as bug list)
Environment:
Last Closed: 2018-09-04 02:32:21 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2607 None None None 2018-09-04 02:33 EDT

  None (edit)
Comment 14 Samikshan Bairagya 2017-07-26 06:40:26 EDT
Upstream patch: https://review.gluster.org/#/c/17813/
Comment 18 Bala Konda Reddy M 2018-05-03 08:07:37 EDT
Build: 3.12.2-8

Stop glusterd and bring down the NIC of the machine.(ifdown <interface>)
Now started glusterd and without any issues, glusterd is able to start.

Marking it to verified according to comment 14
Comment 20 errata-xmlrpc 2018-09-04 02:32:21 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2607

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