@Rachael This looks like it is already being tracked with https://bugzilla.redhat.com/show_bug.cgi?id=1840539. Shall we close this one?
Ah I missed the difference in the scenario. It's the same root cause so there will be a single fix.
Hello Neha, I think - since a single fix can solve the issue, then making changes to the current ocs-osd-removal job process would do it.
Opened a PR- https://github.com/openshift/ocs-operator/pull/589
patch not backported yet. MODIFIED
(In reply to Michael Adam from comment #13) > patch not backported yet. MODIFIED POST and not MODIFIED is what I wanted to say ;-)
https://github.com/openshift/ocs-operator/pull/608 backport PR.
merged
@Neha Yes. The new fix for Bug 1840539 would make an effect. We should wait for the fix.
The fix[1] for Bug 1840539 is merged [1]https://github.com/openshift/ocs-operator/pull/671
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 (Red Hat OpenShift Container Storage 4.5.0 bug fix and enhancement update), 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-2020:3754