Bug 2296535

Summary:	[4.13.z clone] storagecluster CR is not updated with latest apis after storagesystem is marked as its owner
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Nikhil Ladha <nladha>
Component:	odf-operator	Assignee:	Nikhil Ladha <nladha>
Status:	ASSIGNED ---	QA Contact:	Elad <ebenahar>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.13	CC:	ebenahar, kramdoss, muagarwa, nladha, odf-bz-bot, pbalogh
Target Milestone:	---	Flags:	nladha: needinfo- nladha: needinfo? (ebenahar)
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	2296521	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:	2296536, 2296521
Bug Blocks:	2296522, 2296533

Description Nikhil Ladha 2024-07-09 10:43:08 UTC

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

Description of problem (please be detailed as possible and provide log
snippests):
When we create storagecluster the odf-operator creates storagesystem that is added as the ownerref for storagecluster and when that update is done it uses the spec of storagecluster present in odf-operator codebase (vendor directory) to update it, and that's the reason the latest apis under ocs-operator is removed.


Version of all relevant components (if applicable):
4.16


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
N.A


Is there any workaround available to the best of your knowledge?
Update the storagecluster CR, after the ownerref is added to it.


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1


Can this issue reproducible?
Yes


Can this issue reproduce from the UI?
No


If this is a regression, please provide more details to justify this:
New ODF Deployments with custom values for upgrade reliability params will be overridden.

Steps to Reproduce:
1. Deploy ODF Cluster
2. Create a storagecluster from the CLI and provide custom values for cephConfig.
3. The custom values will be removed as soon as the ownerref of the storagecluster is updated.


Actual results:
The CR is overridden with default values and older storagecluster API.


Expected results:
The CR shouldn't be overridden with default values and use the latest storagecluster API.

Additional info:
Reference bug: https://bugzilla.redhat.com/show_bug.cgi?id=2276694#c27