Bug 1728645

Summary: wait for gluster-blockd termination which is running in background before restarting it through systemd
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: RamaKasturi <knarra>
Component: gluster-blockAssignee: Prasanna Kumar Kalever <prasanna.kalever>
Status: CLOSED ERRATA QA Contact: RamaKasturi <knarra>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: ocs-3.11CC: kramdoss, pkarampu, pprakash, prasanna.kalever, puebele, rhs-bugs, rtalur, sabose, vbellur, xiubli
Target Milestone: ---Keywords: TestBlocker, ZStream
Target Release: OCS 3.11.z Batch Update 4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gluster-block-0.2.1-34.el7 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-30 12:33:28 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:    
Bug Blocks: 1699209    

Description RamaKasturi 2019-07-10 10:55:05 UTC 
Description of problem:
When the upgrade activities script finishes and exit successfully,
the gluster-blockd daemon running in the background may still not
killed, so this will be a problem when the gluster-block service
try to start:

ERROR: gluster-blockd is already running...

Version-Release number of selected component (if applicable):
gluster-block-0.2.1-33.el7rhgs.x86_64



How reproducible:
Always

Steps to Reproduce:
1. Install latest OCS3.11.4 bits with LMR
2.
3.

Actual results:
I see that the install fails since gluster-blockd is in inactive state.

Expected results:
gluster-blockd should be in active state and install should not fail.

Additional info:
Comment 3 Prasanna Kumar Kalever 2019-07-10 11:14:14 UTC 
PR: https://github.com/gluster/gluster-block/pull/246
Comment 11 errata-xmlrpc 2019-10-30 12:33:28 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/RHBA-2019:3256