Bug 2308144

Summary:	Incorrect JSON Key Casing and Filtering Logic in createOrUpdateConfigMap Function Leads to Improper ConfigMap
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Vineet <vbadrina>
Component:	odf-dr	Assignee:	Vineet <vbadrina>
odf-dr sub component:	multicluster-orchestrator	QA Contact:	shylesh <shmohan>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	ebenahar, edonnell, muagarwa, nberry, uchapaga
Version:	4.17	Flags:	shmohan: needinfo-
Target Milestone:	---
Target Release:	ODF 4.17.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.17.0-94	Doc Type:	Bug Fix
Doc Text:	.`odf-client-info` config map is now created Previously, the controller inside MCO was not properly filtering the `ManagedClusterView` resource. This lead to a key config map `odf-client-info` to not be created. With this update, the filtering mechanism has been fixed, and `odf-client-info` config map is created as expected.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-10-30 14:32:16 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:	2281703

Description Vineet 2024-08-27 12:26:18 UTC

Description of problem (please be detailed as possible and provide log
snippests):
The issue involves the createOrUpdateConfigMap function in the ManagedClusterViewReconciler controller, where the ConfigMap is not being populated correctly. Specifically, the JSON keys in the ConfigMap are capitalized when they should be lowercase, causing a mismatch with the expected output in test cases. Additionally, there was an issue with filtering YAML keys and setting the Controller field in OwnerReferences.

Version of all relevant components (if applicable):
ODF Multicluster Orchestrator: v4.17.0-84

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

Yes, this issue affects the correct functioning of the reconciliation logic in the ManagedClusterViewReconciler, leading to incorrect ConfigMap data, which in turn can cause issues with downstream processes that rely on this ConfigMap.

Is there any workaround available to the best of your knowledge?

Currently, no workaround is available other than manually correcting the ConfigMap or adjusting the reconciliation logic in the codebase.

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?
Yes, this issue is reproducible consistently in the testing environment.

Can this issue reproduce from the UI?
No, this issue is specific to the backend reconciliation logic and cannot be directly reproduced via the UI.

If this is a regression, please provide more details to justify this:

Steps to Reproduce:
1. Deploy the ODF Multicluster Orchestrator v4.17.0-84.
2. Trigger the reconciliation logic via a ManagedClusterView update.
3. Inspect the resulting ConfigMap (or it may not be created at all ) and compare the JSON keys with the expected format.

Actual results:
It may not be created at all or the ConfigMap contains capitalized JSON keys and may miss certain expected YAML entries.

Expected results:
The ConfigMap should be created and contain lowercase JSON keys and correctly parsed YAML entries when client information is provided in ManagedClusterView

Comment 7 Sunil Kumar Acharya 2024-09-18 12:06:54 UTC

Please update the RDT flag/text appropriately.

Comment 11 errata-xmlrpc 2024-10-30 14:32:16 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 (Important: Red Hat OpenShift Data Foundation 4.17.0 Security, Enhancement, & Bug Fix 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-2024:8676

Comment 12 Red Hat Bugzilla 2025-02-28 04:25:29 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days