Description of problem (please be detailed as possible and provide log snippests): After release of ODF 4.10, we are seeing mcg-operator.v4.10.0 in 4.9.5 Live image Version of all relevant components (if applicable): openshift installer (4.10.6) full_version=4.9.5-5 ( Live 4.9.5 ) Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? not able to install 4.9.5 Ga'ed version Is there any workaround available to the best of your knowledge? NA Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? 2/2 Can this issue reproduce from the UI? not tried If this is a regression, please provide more details to justify this: Yes Steps to Reproduce: 1. Install ODF 4.9.5 GA'ed version 2. check all csv's 3. Actual results: oc get csv NAME DISPLAY VERSION REPLACES PHASE mcg-operator.v4.10.0 NooBaa Operator 4.10.0 Succeeded ocs-operator.v4.9.5 OpenShift Container Storage 4.9.5 ocs-operator.v4.9.4 Succeeded odf-operator.v4.9.5 OpenShift Data Foundation 4.9.5 odf-operator.v4.9.4 Succeeded Expected results: mcg-operator should v4.9.5 Additional info: job: https://ocs4-jenkins-csb-odf-qe.apps.ocp-c1.prod.psi.redhat.com/job/qe-deploy-ocs-cluster-prod/3951/console must gather: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j-053vu1cs33l-uma/j-053vu1cs33l-uma_20220414T061705/logs/failed_testcase_ocs_logs_1649917554/test_deployment_ocs_logs/ Cluster is alive for debugging
Is ODF 4.9.z + OCP 4.10 is a supported version on new installations (after ODF 4.10 is released)?
Earlier we had an impression that the customers who will upgrade from 4.9.5 to 4.9.6 will face this issue but after the internal discussion we figured out that such configurations will not see this BZ. QE can do an upgrade to 4.9.6 and verify. This can only occur for new deployments with ODF 4.9 + OCP 4.10 (AFAIK, this is not supported since ODF 4.10 is released) If this configuration is not supported, the question for QE is why we tested it?
Moving it out again because of unresolved dependencies.
*** Bug 2121149 has been marked as a duplicate of this bug. ***