Description of problem: KubevirtHyperconvergedClusterOperatorCRModification doesn't behave as expected. It is not fired when the resource below are overwritten: - configmap/kubevirt-storage-class-defaults - configmap/v2v-vmware - role/hco.kubevirt.io:config-reader - rolebinding/hco.kubevirt.io:config-reader Also, it is not fired when the counter is increased from zero to one. Version-Release number of selected component (if applicable): 4.8 How reproducible: Steps to Reproduce: 1. Get a new 4.8 setup 2. Edit labels of configmap/v2v-vmware 3. Observe that the alert is not fired 4. Edit labels of kubevirt 5. Observe that the alert is not fired 6. Edit labels of kubevirt again 7. Observe that the alert is fired Additionally, the alert have component_name label and it does only contain the name of operand. This makes troubleshooting harder since name of some operands don't have any clue about their type (e.g. networkaddonsconfigs/cluster) and there are some operands that have the same name but different types (role/hco.kubevirt.io:config-reader and rolebinding/hco.kubevirt.io:config-reader)
The PR below - fixes the behavior for configmaps - fixes the first change issue https://github.com/kubevirt/hyperconverged-cluster-operator/pull/1309/
Note that hco.kubevirt.io:config-reader role/rolebinding are still not strictly reconciled. We have another bug for those objects: https://bugzilla.redhat.com/show_bug.cgi?id=1963963#c0 We think those objects are not critical for the product and we can remove them from the scope of this bug.
missing fixed in version, please add.
After modifying below components: - configmap/kubevirt-storage-class-defaults - configmap/v2v-vmware Able to see the Alert "KubevirtHyperconvergedClusterOperatorCRModification" is generated.
Created attachment 1788210 [details] Screenshot is showing actual results.
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