Bug 1620469

Summary: Brick process NOT ONLINE for heketidb and block-hosting volume
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Atin Mukherjee <amukherj>
Component: glusterdAssignee: Atin Mukherjee <amukherj>
Status: CLOSED ERRATA QA Contact: Bala Konda Reddy M <bmekala>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.4CC: amukherj, apaladug, kramdoss, madam, nberry, pprakash, rhs-bugs, rtalur, sankarshan, sarumuga, sheggodu, storage-qa-internal, vbellur, vdas
Target Milestone: ---   
Target Release: RHGS 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.12.2-17 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1619392
: 1620544 (view as bug list) Environment:
Last Closed: 2018-09-04 06:52:17 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: 1620544    
Bug Blocks: 1503137, 1619392    

Comment 8 Bala Konda Reddy M 2018-08-27 07:02:59 UTC 
Build: 3.12.2-17

1. On a three node cluster with brick-mux enabled 
2. Created 500 volumes and started them.
3. on one node(N1), performed pkill glusterd, pkill gluster.
4. For the first brick of the first volume changed the pid entry in /var/run/gluster/vols/test_1/<brick.pid> to another process pid
5. Started glusterd on node1 N1 and bricks got new pid and no deadlock seen for brick process and all the bricks are online .

All the bricks are up and online not seen any deadlock for glusterfsd. Tried the above scenario couple of times. Didn't hit this issue

Hence moving it to verified.
Comment 10 errata-xmlrpc 2018-09-04 06:52:17 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.

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