Bug 2211853

+++ This bug was initially created as a clone of Bug #2165128 +++

Description of problem (please be detailed as possible and provide log
snippests):


Version of all relevant components (if applicable):
ACM 2.7.0-DOWNSTREAM-2023-01-07-13-58-25
ODF 4.12.0-158 and 4.12.0-167
OCP 4.12.0-0.nightly-2023-01-08-142418


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?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. While creating a Regional DR setup, install 2 different sub-versions of ODF on both the managed clusters (say  4.12.0-158 on C1 and 4.12.0-167 on C2)
2. Now try creating DRPolicy using these 2 clusters
3.


Actual results: DRPolicy creation is restricted if 2 different sub-versions are ODF are installed on the Managed Clusters

Error message on ACM console-
asagare-odfrc has either an unsupported ODF version or the ODF operator is missing, install or update to ODF 4.12.0-158.0 or latest version to enable DR protection.

asagare-odfrc has ODF 4.12.0-167 which should be supported but it always checks the lower version which is 4.12.0-158 on the other managed cluster

Expected results: 2 sub-versions of ODF should be supported for DRPolicy creation


Additional info:

--- Additional comment from RHEL Program Management on 2023-01-27 19:42:45 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 Red Hat Bugzilla on 2023-01-31 23:38:35 UTC ---

remove performed by PnT Account Manager <pnt-expunge>

--- Additional comment from Red Hat Bugzilla on 2023-01-31 23:40:40 UTC ---

remove performed by PnT Account Manager <pnt-expunge>

--- Additional comment from gowtham on 2023-02-01 06:37:59 UTC ---

As per the new change (mail sub: Re-introducing the notion of RC builds to CPaaS build pipeline), All non-rc(including stable) build follows the format of X.Y.Z-RRR.TAG CSV. But rc builds follow  X.Y.Z versioning in their CSVs.

So it won't affect the prod build. But since it is a testing blocker it is better to fix it.

--- Additional comment from Debjyoti Pandit on 2023-02-01 10:52:06 UTC ---

Can you please replicate and share the setup for the same?

--- Additional comment from Aman Agrawal on 2023-02-01 15:39:50 UTC ---

Hi, I don't understand what is there to replicate in this bug? Did you try following the steps at your end and couldn't see this issue?
Bdw, I do not have a setup at the moment.

--- Additional comment from Sanjal Katiyar on 2023-02-07 05:12:35 UTC ---

This BZ is for 4.13, create a clone if we are planning to fix for 4.12.z

--- Additional comment from gowtham on 2023-03-14 06:54:31 UTC ---

As i discussed with QE this is not a blocker, and reduced the severity, fix is targetted for 4.13

--- Additional comment from gowtham on 2023-03-14 06:55:11 UTC ---

4.14 PR: https://github.com/red-hat-storage/odf-console/pull/620

--- Additional comment from Mudit Agarwal on 2023-04-03 11:01:11 UTC ---

Fixed in version: Any latest stable 4.13 build

--- Additional comment from RHEL Program Management on 2023-04-04 16:24:59 UTC ---

This BZ is being approved for ODF 4.13.0 release, upon receipt of the 3 ACKs (PM,Devel,QA) for the release flag 'odf‑4.13.0

--- Additional comment from RHEL Program Management on 2023-04-04 16:24:59 UTC ---

Since this bug has been approved for ODF 4.13.0 release, through release flag 'odf-4.13.0+', the Target Release is being set to 'ODF 4.13.0

--- Additional comment from errata-xmlrpc on 2023-04-17 13:26:54 UTC ---

This bug has been added to advisory RHBA-2023:108078 by Boris Ranto (branto)