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

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

The plan as discussed in MS and product pgm calls is to backport all the fixes for the following two epics of ODF 4.13 to a 4.12.z build which can then be utilized both by MS dev and QE to test and qualify the features and their support in the  new Fusion aaS 
https://issues.redhat.com/browse/RHSTOR-2442 and https://issues.redhat.com/browse/RHSTOR-3194 from 4.13 feature freeze build to 4.12.z 


This bug is raised to request to backport the fixes of https://issues.redhat.com/browse/RHSTOR-2442 to ODF 4.12.z and let us know which build of ODF 4.12.z would be having  this support, for QE to test.


Version of all relevant components (if applicable):


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.
2.
3.


Actual results:


Expected results:


Additional info:

--- Additional comment from RHEL Program Management on 2023-03-01 07:53:22 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 Nitin Goyal on 2023-03-06 11:20:05 UTC ---

For this specific functionality, numerous PRs were pushed to the ocs and odf in the 4.13 release. I am not confident enough to backport these PRs because 4.13 has not yet been tested, but if QE says that 4.13 is stable and everything is working as expected (including this new feature), I might try to do so.

--- Additional comment from Mudit Agarwal on 2023-03-20 07:16:14 UTC ---

Nitin, we have the qe ack. They have not tested this in 4.13 and ok to get it in 4.12.z on the basis of regression only.
Lets proceed with the backport. Use this BZ as a placholder.

--- Additional comment from Mudit Agarwal on 2023-03-20 08:06:07 UTC ---

As per the discussions with QE/MS team we want to move this to 4.12.3. So, lets not backport now.

--- Additional comment from Nitin Goyal on 2023-03-20 13:15:46 UTC ---

After a long discussion, we came to the conclusion that we wanted to backport the feature though customers won't be using it until QE qualifies it.

--- Additional comment from RHEL Program Management on 2023-03-24 10:03:19 UTC ---

The 'Target Release' is not to be set manually at the Red Hat OpenShift Data Foundation product.

The 'Target Release' will be auto set appropriately, after the 3 Acks (pm,devel,qa) are set to "+" for a specific release flag and that release flag gets auto set to "+".

--- Additional comment from RHEL Program Management on 2023-03-24 10:03:19 UTC ---

This BZ is being approved for an ODF 4.12.z z-stream update, upon receipt of the 3 ACKs (PM,Devel,QA) for the release flag 'odf‑4.12.z', and having been marked for an approved z-stream update

--- Additional comment from RHEL Program Management on 2023-03-24 10:03:19 UTC ---

Since this bug has been approved for ODF 4.12.2 release, through release flag 'odf-4.12.z+', and appropriate update number entry at the 'Internal Whiteboard', the Target Release is being set to 'ODF 4.12.2'

--- Additional comment from Boris Ranto on 2023-03-27 07:24:56 UTC ---

The feature is not complete upstream yet. There is no sense blocking 4.12.2 on this, moving it to 4.12.3.

--- Additional comment from RHEL Program Management on 2023-03-27 07:25:06 UTC ---

Since this bug has been approved for ODF 4.12.2 release, through release flag 'odf-4.12.z+', and appropriate update number entry at the 'Internal Whiteboard', the Target Release is being set to 'ODF 4.12.2'

--- Additional comment from Neha Berry on 2023-03-29 13:53:58 UTC ---

Hi Mudit, Nitin,

Let us know if any RC build of 4.12.2 is available with this backport yet

cc @dbindra

--- Additional comment from Nitin Goyal on 2023-03-29 14:18:08 UTC ---

Build mail with the subject `Release Candidate ODF 4.12 build '4.12.2-2' is available and ready for testing` have these fixes.

--- Additional comment from Boris Ranto on 2023-03-30 10:28:04 UTC ---

OK, it looks like there actually are two bzs for this but with almost the same title (just a different JIRA ID). In this case, we can attach this bz to the errata for 4.12.2 as these changes are in.

--- Additional comment from errata-xmlrpc on 2023-03-30 10:28:46 UTC ---

Bug report changed to ON_QA status by Errata System.
A QE request has been submitted for advisory RHSA-2023:111844-01
https://errata.devel.redhat.com/advisory/111844

--- Additional comment from errata-xmlrpc on 2023-03-30 10:28:56 UTC ---

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