Bug 2185012

Summary:	[Tracker in MS] [ Fusion-aaS]Remove storageclassclaim cr and create new cr storageclass request cr
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Neha Berry <nberry>
Component:	odf-managed-service	Assignee:	Ohad <omitrani>
Status:	NEW ---	QA Contact:	Neha Berry <nberry>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.13	CC:	fbalak, jijoy, nberry, odf-bz-bot, sgatfane, srai
Target Milestone:	---	Keywords:	AutomationBackLog, Tracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2184769	Environment:
Last Closed:		Type:	---
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:	2184769, 2186443
Bug Blocks:

Description Neha Berry 2023-04-06 13:59:28 UTC

+++ This bug was initially created as a clone of Bug #2184769 +++ for the fix to be to be backported to 4.12.z

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

Remove storageclassclaim cr and create new cr storageclassrequest. The consumer cr and code have moved to the new operator so removing the cr and code.

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-04-05 16:50:10 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.