Bug 1598356 – delay gluster-blockd start until all bricks comeup

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1598356 - delay gluster-blockd start until all bricks comeup

Summary:	delay gluster-blockd start until all bricks comeup

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Gluster Storage
Classification:	Red Hat
Component:	glusterd (Show other bugs)
Sub Component:
Version:	3.4
Hardware:	Unspecified Unspecified

Priority	unspecified Severity high
Target Milestone:	---
Target Release:	RHGS 3.4.0
Assigned To:	Pranith Kumar K
QA Contact:	Bala Konda Reddy M
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1597568
Blocks:	1503137
	Show dependency tree / graph

Reported:	2018-07-05 03:59 EDT by Pranith Kumar K
Modified:	2018-09-04 02:51 EDT (History)
CC List:	15 users (show)

See Also:
Fixed In Version:	glusterfs-3.12.2-14
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:	1598353
Environment:
Last Closed:	2018-09-04 02:50:20 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)
Add an attachment (proposed patch, testcase, etc.)

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

Groups: None (edit)

Comment 3 nchilaka 2018-07-05 07:25:15 EDT

giving ack after discussing with component qe

Comment 9 Bala Konda Reddy M 2018-08-20 08:01:08 EDT

Glusterfs Build:  glusterfs-3.12.2-16
Block Build: gluster-block-0.2.1-24

1. On a three node cluster, created 200 replica(1X3) volumes
2. Created 500 block devices for random volumes.
3. Performed reboot on one node.
4. Once the node is up and running gluster-blockd service didn't started until all the bricks are online.
5. gluster-blockd started after all the bricks are up.

Hence marking it as verified

Comment 10 errata-xmlrpc 2018-09-04 02:50:20 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.