+++ This bug was initially created as a clone of Bug #2174336 +++ 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 ODF 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 f This bug is raised to request to backport the fixes of https://issues.redhat.com/browse/RHSTOR-3194 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:59:43 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 Madhu Rajanna on 2023-03-13 08:52:01 UTC --- Neha, what is the ask here? Is it to build the ocs-client-operator with ODF 4.12? --- Additional comment from Neha Berry on 2023-03-20 07:46:30 UTC --- (In reply to Madhu Rajanna from comment #2) > Neha, what is the ask here? Is it to build the ocs-client-operator with ODF > 4.12? Hey Madhu, Apologies but I am not aware of it completely. I was suggested to raise a backport PR for the whole 4.13 feature https://issues.redhat.com/browse/RHSTOR-3194 to be included in the 4.12.2 build I am not aware of the breakups as you asked. --- 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 RHEL Program Management on 2023-04-05 05:47:32 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-04-17 11:48:29 UTC --- The testing of the feature for happy path is completed and QE gives an ack on backporting the entire feature to 4.12.3 build. --- Additional comment from Jilju Joy on 2023-04-17 15:39:02 UTC --- Happy path validation is tracked in https://issues.redhat.com/browse/RHSTOR-4480. Testing was done in ODF 4.13.0 without agent based deployment. Agent based deployment is not available with ODF 4.13.0.