Bug 1676633

Summary: gluster-blockd services is not up after upgrading to the latest RHGS BU3 bits.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: RamaKasturi <knarra>
Component: gluster-blockAssignee: Prasanna Kumar Kalever <prasanna.kalever>
Status: CLOSED ERRATA QA Contact: Arun Kumar <arukumar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: ocs-3.11CC: arukumar, knarra, kramdoss, pkarampu, pprakash, prasanna.kalever, puebele, rhs-bugs, sankarshan, vbellur, xiubli
Target Milestone: ---Keywords: ZStream
Target Release: OCS 3.11.z Batch Update 2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gluster-block-0.2.1-31.el7rhgs Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1679910 (view as bug list) Environment:
Last Closed: 2019-03-27 04:55:19 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: 1679910    

Description RamaKasturi 2019-02-12 17:54:51 UTC 
Description of problem:
I see that after upgrading RHGS bits from BU2 to BU3 and running systemctl status gluster-blockd service it asks me to reload the daemon by running the command 'systemctl daemon-reload"


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

How reproducible:
Hit it once

Steps to Reproduce:
1. Upgraded the independent setup from BU2 to BU3
2. Run the command systemctl status gluster-blockd
3. 

Actual results:
output from the service says to reload the daemon.

Expected results:
gluster-blockd daemon should be running and should not ask me to reload.

Additional info:
Comment 6 Prasanna Kumar Kalever 2019-02-19 05:35:38 UTC 
Upstream PR merged long back: https://review.gluster.org/#/c/gluster-block/+/18335/
Comment 18 Prasanna Kumar Kalever 2019-03-13 09:12:28 UTC 
Looks good to me, Thanks!
Comment 20 errata-xmlrpc 2019-03-27 04:55:19 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:0665