Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1294412 - [RFE] : Start glusterd even when the glusterd is unable to resolve the bricks path.
[RFE] : Start glusterd even when the glusterd is unable to resolve the bricks...
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd (Show other bugs)
3.1
Unspecified Unspecified
unspecified Severity medium
: ---
: RHGS 3.4.0
Assigned To: Atin Mukherjee
Bala Konda Reddy M
rebase
: FutureFeature, ZStream
Depends On: 1036551
Blocks: 1503132
  Show dependency treegraph
 
Reported: 2015-12-28 01:06 EST by Atin Mukherjee
Modified: 2018-09-04 02:29 EDT (History)
9 users (show)

See Also:
Fixed In Version: glusterfs-3.12.2-1
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1036551
Environment:
Last Closed: 2018-09-04 02:27:31 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:29 EDT

  None (edit)
Comment 3 Atin Mukherjee 2017-08-07 04:14:00 EDT
upstream patch : https://review.gluster.org/#/c/17813/
Comment 7 Bala Konda Reddy M 2018-04-04 05:56:35 EDT
Build : 3.12.2-6

In 3.3.1, glusterd fails to start and bricks will be offline. With the fix in 3.4.0, glusterd started and bricks are online. 

1. Created a volume using 4 nodes and started it
2. Stopped glusterd on one of the node.
3. Bring down the network.
4. Start the glusterd on the node where it was stopped.
5. Glusterd started without any issues and bricks are online

Hence marking it as verified
Comment 9 errata-xmlrpc 2018-09-04 02:27:31 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.