Description of problem (please be detailed as possible and provide log snippests): From the logs here: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j-264vu1cs33-ua/j-264vu1cs33-ua_20220811T141729/logs/failed_testcase_ocs_logs_1660230528/test_upgrade_ocs_logs/ocs_must_gather/quay-io-rhceph-dev-ocs-must-gather-sha256-1af7fca2436df817cd3158e9d3a180d6d3ab1f6ac40a509a0ec3f378ac29ed2c/namespaces/openshift-storage/oc_output/csv I see that the upgrade is stuck in pending state. ocs-operator.v4.10.5 OpenShift Container Storage 4.10.5 ocs-operator.v4.10.4 Replacing ocs-operator.v4.11.1 OpenShift Container Storage 4.11.1 ocs-operator.v4.10.5 Pending Version of all relevant components (if applicable): Upgrade from 4.10.5 to this build quay.io/rhceph-dev/ocs-registry:4.11.1-3 Which suppose to be: test build based on RHCS 5.3 with upgrades enabled Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? Haven't tried yet. Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Install 4.10.5 2. Upgrade to mentioned build 4.11.1-3 3. Actual results: Upgrade is stuck Expected results: Have upgrade completed Additional info: Must gather logs http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j-264vu1cs33-ua/j-264vu1cs33-ua_20220811T141729/logs/failed_testcase_ocs_logs_1660230528/test_upgrade_ocs_logs/
Moving to 4.11.z while we try to repro this
Please reopen if this is seen again