Bug 2100415

Summary: HCO is taking too much time for reconciling kubevirt-plugin deployment
Product: Container Native Virtualization (CNV) Reporter: Satyajit Bulage <sbulage>
Component: InstallationAssignee: Oren Cohen <ocohen>
Status: CLOSED ERRATA QA Contact: Natalie Gavrielov <ngavrilo>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.11.0CC: cnv-qe-bugs, dbasunag, kmajcher, stirabos
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: CNV v4.11.0-552, HCO v4.11.0-93 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-09-14 19:36:10 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 Satyajit Bulage 2022-06-23 10:11:06 UTC
Description of problem: On SNO cluster, I need to match the resourceVersion from HCO related object's resourceVersion. I manually added labels and waited for some time to get reconcile it. It took more than 1 min to reconcile and restore back to it's original state.


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


How reproducible:100% (Seen on SNO cluster)


Steps to Reproduce:
1. Add manually label to deployment --> kubevirt-plugin
2. Check the resourceVersion (note it down)
3. Check the HCO relatedObjects in the under Status.

Actual results: Both values are different and not matching, it is happened due to HCO didn't reconciled on time to reflect the correct values.


Expected results: Both values should be equal and HCO should reconcile it immediately like other resources.


Additional info:

Comment 1 Debarati Basu-Nag 2022-06-23 13:43:26 UTC
Current automation does the following steps:
1) Add a new label to kubevirt-plugin and wait for 10 minutes for it to revert back.
2) Wait for 3 minutes for the resourceVersion of kubevirt-plugin to change from the one before label addition.
3) Wait for 10 minutes for hco.status.relatedObject to reflect the new resource version - to conclude reconciliation completed.
Currently we are failing intermittently in 3rd step.

Comment 4 Satyajit Bulage 2022-07-07 09:07:40 UTC
I am able to see the resourceVersions are matching.
Verifying it.

Comment 7 errata-xmlrpc 2022-09-14 19:36:10 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: OpenShift Virtualization 4.11.0 Images security and 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-2022:6526