Description of problem: During cnv upgrade v4.11.4-119 to 4.11.5 (ocp version being 4.11.45), noticed KubevirtHyperconvergedClusterOperatorCRModification alert in a firing state. How reproducible: 100% Steps to Reproduce: 1. Check alerts fired during cnv upgrade 2. 3. Actual results: (sample) [{'labels': {'alertname': 'KubevirtHyperconvergedClusterOperatorCRModification', 'component_name': 'imagestream/rhel8-guest', 'kubernetes_operator_component': 'hyperconverged-cluster-operator', 'kubernetes_operator_part_of': 'kubevirt', 'severity': 'warning'}, 'annotations': {'description': 'Out-of-band modification for imagestream/rhel8-guest.', 'runbook_url': 'https://kubevirt.io/monitoring/runbooks/KubevirtHyperconvergedClusterOperatorCRModification', 'summary': '1 out-of-band CR modifications were detected in the last 10 minutes.'}, 'state': 'firing', 'activeAt': '2023-07-19T19:53:45.483162627Z', 'value': '1e+00'}, { full log: http://pastebin.test.redhat.com/1105658 Expected results: no alerts should fire during cnv upgrade processs Additional info:
Dharmit, please see if you can reproduce and try to fix
https://bugzilla.redhat.com/show_bug.cgi?id=2154319 this was fixed in 4.13.1. Do we want to backport this?
*** This bug has been marked as a duplicate of bug 2227785 ***