Cloning for 4.12.z backport +++ This bug was initially created as a clone of Bug #2175111 +++ Description of problem (please be detailed as possible and provide log snippests): Version of all relevant components (if applicable): MCO - 4.12.0 OCP - 4.12-ga 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? No 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? Yes Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Keep the cluster in 4.12.0 2. Edit the "image" tag in catsrc to 4.12.1 image Actual results: Upgrade of MCO and other DR operators didn't happen Expected results: All the relevant DR operators should be upgraded Additional info: --- Additional comment from RHEL Program Management on 2023-03-03 08:32:35 UTC --- This bug having no release flag set previously, is now set with release flag 'odf‑4.13.0' to '?', and so is being proposed to be fixed at the ODF 4.13.0 release. Note that the 3 Acks (pm_ack, devel_ack, qa_ack), if any previously set while release flag was missing, have now been reset since the Acks are to be set against a release flag. --- Additional comment from umanga on 2023-03-03 08:51:40 UTC --- SkipRange annotation is missing on multicluster operator CSV due to which upgrades from 4.12.0 to 4.12.1 or 4.12.z to 4.13.0 won't work. This is a regression in 4.12 and 4.13. Adding devel_ack+. --- Additional comment from RHEL Program Management on 2023-03-03 08:51:48 UTC --- This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being proposed as a blocker for this release. Please resolve ASAP.
We have some issue with bot, if you have both devel and qe ack then go ahead and merge the PR
Change merged, should be available in next build.
Fixed in 4.12.2-2.
Verification comments Actual issue - Upgrade from 4.12.0 - 4.12.1 was failing As part of verification, did upgrade from 4.12.1 to 4.12.2-2, upgrade was successful Must gather:- c1 - http://rhsqe-repo.lab.eng.blr.redhat.com/OCS/ocs-qe-bugs/BZ-2080365/c1/must-gather.local.3847576541802389652/quay-io-rhceph-dev-ocs-must-gather-sha256-42e21aeadcaeff809b877661f236b482ca1dcd563bab345fe02c2e86945121eb/ c2 - http://rhsqe-repo.lab.eng.blr.redhat.com/OCS/ocs-qe-bugs/BZ-2080365/c2/must-gather.local.413411229073577119/quay-io-rhceph-dev-ocs-must-gather-sha256-42e21aeadcaeff809b877661f236b482ca1dcd563bab345fe02c2e86945121eb/ Hub - http://rhsqe-repo.lab.eng.blr.redhat.com/OCS/ocs-qe-bugs/BZ-2080365/hub/must-gather.local.7056620973765675956/quay-io-rhceph-dev-ocs-must-gather-sha256-42e21aeadcaeff809b877661f236b482ca1dcd563bab345fe02c2e86945121eb/
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 (Moderate: Red Hat OpenShift Data Foundation 4.12.2 Bug Fix and security 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/RHSA-2023:1816