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:
Upstream PR merged long back: https://review.gluster.org/#/c/gluster-block/+/18335/
Looks good to me, Thanks!
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