Created attachment 1763037 [details] Incorrect infra configuration. Description of problem: Incorrect information related to infra configuration provided to KubeVirt CR through the HCO spec is being accepted. Version-Release number of selected component (if applicable):4.8 How reproducible:100% Steps to Reproduce: 1.Add attached yaml contents in the HCO CR spec 2.Observe the HCO CR status in the UI as well as CLI Actual results: Changes to HCO CR are propagated to KubeVirt CR which is accepted which leads to HCO CR keeping itself in Progressing state and never completes. Expected results: Changes made to the Infra under HCO CR spec should be refused by KubeVirt CR as they are incorrect. Additional info:In the attached example the wrong part of the configuration is the "Equal" operand which doesn't exists. HCO CR refuse to update incorrect changes which is fixed in the BZ(https://bugzilla.redhat.com/show_bug.cgi?id=1893646).
Igor, I've targetted this to the 4.8.0 release because it appears the problem is well understood and the scope of the problem is limited. I've assigned it to you as you appear to have been involved in fixing the issue on the HCO side. Please advise if I'm mistaken.
Hi You are correct, I was involved in this case and I managed to reproduce this issue on our side: - disable HCO - edit KV CR - put the wrong value - configuration applied while should be rejected Will start working on this issue.
Can we get an update on the status please? This is blocking automation.
Work in progress on this issue. PR will be ready soon
Deferring due to capacity.
Is it possible this can be targeted to a 4.8.Z stream?
I can reproduce this with 4.8 verify with build: v4.9.1-4 step: 1. deploy 4.9.1 on PSI 2. edit kubevirt CR from webUI or CLI add below: spec: infra: nodePlacement: tolerations: - key: "foo" value: "bar" operator: "nonexistingOperatorString" spec: workloads: nodePlacement: tolerations: - key: "foo" value: "bar" operator: "nonexistingOperatorString" when saved config, will get syntax error immediately: Error "Unsupported value: "nonexistingOperatorString": supported values: "Equal", "Exists"" for field "spec.template.spec.tolerations[0].operator". I also test yaml contents from bug description infra: nodePlacement: affinity: nodeAffinity: requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: - key: role.kubernetes.io/master operator: Equal values: - "" tolerations: - effect: NoSchedule key: master operator: Exists when saved config, will get syntax error immediately: Error "Invalid value: "Equal": not a valid selector operator" for field "spec.template.spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[0].operator". move to verified.
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 (OpenShift Virtualization 4.9.1 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/RHBA-2021:5091