Bug 1598356 - delay gluster-blockd start until all bricks comeup
Summary: delay gluster-blockd start until all bricks comeup
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: RHGS 3.4.0
Assignee: Pranith Kumar K
QA Contact: Bala Konda Reddy M
Depends On: 1597568
Blocks: 1503137
TreeView+ depends on / blocked
Reported: 2018-07-05 07:59 UTC by Pranith Kumar K
Modified: 2018-09-04 06:51 UTC (History)
15 users (show)

Fixed In Version: glusterfs-3.12.2-14
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1598353
Last Closed: 2018-09-04 06:50:20 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2607 None None None 2018-09-04 06:51:44 UTC

Comment 3 nchilaka 2018-07-05 11:25:15 UTC
giving ack after discussing with component qe

Comment 9 Bala Konda Reddy M 2018-08-20 12:01:08 UTC
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 06:50:20 UTC
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.


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