Description of problem: ----------------------- On a fresh deployment of OCP 3.10 and OCS 3.11.1 builds, the block PVC is not getting Bound even after applying the workaround which was given here, https://bugzilla.redhat.com/show_bug.cgi?id=1660280#c33 . Version-Release number of selected component (if applicable): OCP 3.10.101 ans OCS 3.11.1 Steps to Reproduce: 1. Deploy OCP 3.10.101 and OCS 3.11.1 2. After the deployment is successful create a block pvc using the default Storage class 3. The block PVC should get Bound. But as in this case it did not, once the PVC creation fails, follow steps given here, https://bugzilla.redhat.com/show_bug.cgi?id=1660280#c33 4. Try to create a new block PVC. Actual results: The block PVC is not in Bound even after following the steps given in https://bugzilla.redhat.com/show_bug.cgi?id=1660280#c33. Expected results: The block PVC should get bound without following the steps given in https://bugzilla.redhat.com/show_bug.cgi?id=1660280#c33. Additional info:
If you can still recreate this issue, please provide the heketi and glusterblock-provisioner pod logs.
As this is working in the latest bits and has been successfully verified. Clearing my needinfo.
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:0670