Description of problem: Tried to perform an upgrade from ocs3.11.3 to ocs3.11.4 and i see that the bricks on which the pod is upgraded does not come online even after the pod is up & running. Version-Release number of selected component (if applicable): ocs3.11.4 How reproducible: 1/1 Steps to Reproduce: 1. Install OCS3.11.3 setup 2. Now upgrade one of the glusterpod to OCS3.11.4 3. Actual results: I see that pod is up and running, but all the bricks where the pod is upgraded is offline and i also do not see the shd to be up and running. Expected results: All the bricks in the upgraded pod/node should be up & Running. Additional info: I see that there is already a bug for shd not being up. https://bugzilla.redhat.com/show_bug.cgi?id=1721802
Saravana/Talur, we have to bring the vol option as specified in the RHGS bug.
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:3257