Bug 1968196

Summary:	[strict reconciliation] resourceVersion not updated in HCO CR relatedObjects entry for kubevirt-storage-class-defaults
Product:	Container Native Virtualization (CNV)	Reporter:	ibesso <ibesso>
Component:	Installation	Assignee:	Simone Tiraboschi <stirabos>
Status:	CLOSED ERRATA	QA Contact:	Inbar Rose <irose>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.8.0	CC:	cnv-qe-bugs, stirabos
Target Milestone:	---
Target Release:	4.8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	hco-bundle-registry-container-v4.8.0-388	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-27 14:32:39 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:

Description ibesso 2021-06-06 17:34:58 UTC

Description of problem:
----------------------
After modifying successfully the HCO CR by adding a new key with its value (localStorageClassName: myLocalStorageClassName), the changes are saved in the HCO CR, propagated to the appropriate configmap (kubevirt-storage-class-defaults), but the corresponding resourceVersion in the HCO CR's relatedObjects is not updated.

Version-Release number of selected component (if applicable):
------------------------------------------------------------
4.8.0


How reproducible:
----------------
100%


Steps to Reproduce:
1. Check the resourceVersion of kubevirt-storage-class-defaults configmap in HCO CR's relatedObjects list.

2. Add the following to HCO CR spec:
localStorageClassName: myLocalStorageClassName

3. Examine the kubevirt-storage-class-defaults configmap (to verify that changes were propagated properly)

4. Repeat step 1.

Actual results:
--------------
[OK] the following was added to the kubevirt-storage-class-defaults configmap:

“myLocalStorageClassName.accessMode": "ReadWriteOnce"
“myLocalStorageClassName.volumeMode": "Filesystem"

[NOT OK] the resourceVersion from step 1 and step 4 are identical.


Expected results:
----------------
the resourceVersion should have been changed.


Additional info:
---------------
There is another configmap in which this bug DOES NOT occur, i.e. working properly: v2v-vmware configmap.

Comment 1 ibesso 2021-06-10 14:29:34 UTC

Verified on CNV 4.8.0 (hco-bundle-registry-container-v4.8.0-388) (registry-proxy.engineering.redhat.com/rh-osbs/iib:80270)
--------------------------------------------------------------------------------------------------------------------------
This bug was found using the automation I wrote: modifying certain fields and verifying the objects/CRs HCO controls.
The single test that failed was on this configmap.

Re-running all the tests with the aforementioned build, resulted in flawless success (including this particular test that failed).
Moving to VERIFIED.

Comment 4 errata-xmlrpc 2021-07-27 14:32:39 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: OpenShift Virtualization 4.8.0 Images), 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-2021:2920