1) watch clusteroperator/kube-storage-version-migrator 2) delete operand namespace - openshift-kube-storage-version-migrator 3) wait - it should return via its operator, kube-storage-version-migrator-operator - waited for at least 10min - clusteroperator is Degraded=True during this time, but operand namespace never returns 4) refresh kube-storage-version-migrator-operator pod in openshift-kube-storage-version-migrator-operator namespace 5) only after the operator pod comes back does its operand namespace return, CO status Progressing=true/Degraded=False, then few seconds after Progressing=False The operator should restore its operand namespace. Steps 4,5 should not be necessary.
Verified with OCP 4.5.0-0.nightly-2020-05-30-025738, $ oc get namespaces | grep openshift-kube-storage-version-migrator openshift-kube-storage-version-migrator Active 6h3m openshift-kube-storage-version-migrator-operator Active 6h13m $ oc delete namespaces openshift-kube-storage-version-migrator namespace "openshift-kube-storage-version-migrator" deleted $ oc get namespaces | grep openshift-kube-storage-version-migrator openshift-kube-storage-version-migrator Active 18s openshift-kube-storage-version-migrator-operator Active 6h14m $ oc get co NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE ... kube-storage-version-migrator 4.5.0-0.nightly-2020-05-30-025738 True False False 17s ... From above results, the namespace openshift-kube-storage-version-migrator returned back quickly as expected, move the bug verified.
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-2020:2409