Bug 2174335

Summary:	[Backport to 4.12.z] Placeholder bug to backport the odf changes for Managed services epic RHSTOR-2442 to 4.12.z
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Neha Berry <nberry>
Component:	unclassified	Assignee:	Nitin Goyal <nigoyal>
Status:	CLOSED ERRATA	QA Contact:	Jilju Joy <jijoy>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.12	CC:	branto, dbindra, kramdoss, muagarwa, nigoyal, ocs-bugs, odf-bz-bot
Target Milestone:	---
Target Release:	ODF 4.12.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2184653 (view as bug list)		Environment:
Last Closed:	2023-04-17 22:34:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2184653

Description Neha Berry 2023-03-01 07:53:15 UTC

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:

Comment 3 Mudit Agarwal 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.

Comment 4 Mudit Agarwal 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.

Comment 13 Boris Ranto 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.

Comment 16 Jilju Joy 2023-04-05 11:08:26 UTC

Verifying based on the regression runs of ODF 4.12.2. No issues were observed due to this change.
Testing in MS will be tracked in the bug https://bugzilla.redhat.com/show_bug.cgi?id=2184653

Comment 21 errata-xmlrpc 2023-04-17 22:34:07 UTC

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