Description of problem: Obsolete CPU models (set in kubevirt-cpu-plugin-configmap) are set on worker nodes. Version-Release number of selected component (if applicable): kubevirt-ssp-operator-container-v2.6.0-29 How reproducible: 100% Steps to Reproduce: 1. Deploy CNV 2. Check the CPU models set on the worker nodes Actual results: Obsolete CPU models are set Expected results: Obsolete CPU models should not be set Additional info: ============================================================= $ oc get cm -n openshift-cnv kubevirt-cpu-plugin-configmap -oyaml apiVersion: v1 data: cpu-plugin-configmap.yaml: |- obsoleteCPUs: - "486" - "pentium" - "pentium2" - "pentium3" - "pentiumpro" - "coreduo" - "n270" - "core2duo" - "Conroe" - "athlon" - "phenom" minCPU: "Penryn" ============================================================= $ oc describe node ssp05-tzl2g-worker-0-jzlq2 |grep cpu-model feature.node.kubernetes.io/cpu-model-486=true feature.node.kubernetes.io/cpu-model-Conroe=true feature.node.kubernetes.io/cpu-model-Haswell-noTSX=true feature.node.kubernetes.io/cpu-model-Haswell-noTSX-IBRS=true feature.node.kubernetes.io/cpu-model-IvyBridge=true feature.node.kubernetes.io/cpu-model-IvyBridge-IBRS=true feature.node.kubernetes.io/cpu-model-Nehalem=true feature.node.kubernetes.io/cpu-model-Nehalem-IBRS=true feature.node.kubernetes.io/cpu-model-Opteron_G1=true feature.node.kubernetes.io/cpu-model-Opteron_G2=true feature.node.kubernetes.io/cpu-model-Penryn=true feature.node.kubernetes.io/cpu-model-SandyBridge=true feature.node.kubernetes.io/cpu-model-SandyBridge-IBRS=true feature.node.kubernetes.io/cpu-model-Westmere=true feature.node.kubernetes.io/cpu-model-Westmere-IBRS=true feature.node.kubernetes.io/cpu-model-core2duo=true feature.node.kubernetes.io/cpu-model-coreduo=true feature.node.kubernetes.io/cpu-model-kvm32=true feature.node.kubernetes.io/cpu-model-kvm64=true feature.node.kubernetes.io/cpu-model-n270=true feature.node.kubernetes.io/cpu-model-pentium=true feature.node.kubernetes.io/cpu-model-pentium2=true feature.node.kubernetes.io/cpu-model-pentium3=true feature.node.kubernetes.io/cpu-model-qemu32=true feature.node.kubernetes.io/cpu-model-qemu64=true node-labeller-feature.node.kubernetes.io/cpu-model-486: true node-labeller-feature.node.kubernetes.io/cpu-model-Conroe: true node-labeller-feature.node.kubernetes.io/cpu-model-Haswell-noTSX: true node-labeller-feature.node.kubernetes.io/cpu-model-Haswell-noTSX-IBRS: true node-labeller-feature.node.kubernetes.io/cpu-model-IvyBridge: true node-labeller-feature.node.kubernetes.io/cpu-model-IvyBridge-IBRS: true node-labeller-feature.node.kubernetes.io/cpu-model-Nehalem: true node-labeller-feature.node.kubernetes.io/cpu-model-Nehalem-IBRS: true node-labeller-feature.node.kubernetes.io/cpu-model-Opteron_G1: true node-labeller-feature.node.kubernetes.io/cpu-model-Opteron_G2: true node-labeller-feature.node.kubernetes.io/cpu-model-Penryn: true node-labeller-feature.node.kubernetes.io/cpu-model-SandyBridge: true node-labeller-feature.node.kubernetes.io/cpu-model-SandyBridge-IBRS: true node-labeller-feature.node.kubernetes.io/cpu-model-Westmere: true node-labeller-feature.node.kubernetes.io/cpu-model-Westmere-IBRS: true node-labeller-feature.node.kubernetes.io/cpu-model-core2duo: true node-labeller-feature.node.kubernetes.io/cpu-model-coreduo: true node-labeller-feature.node.kubernetes.io/cpu-model-kvm32: true node-labeller-feature.node.kubernetes.io/cpu-model-kvm64: true node-labeller-feature.node.kubernetes.io/cpu-model-n270: true node-labeller-feature.node.kubernetes.io/cpu-model-pentium: true node-labeller-feature.node.kubernetes.io/cpu-model-pentium2: true node-labeller-feature.node.kubernetes.io/cpu-model-pentium3: true node-labeller-feature.node.kubernetes.io/cpu-model-qemu32: true node-labeller-feature.node.kubernetes.io/cpu-model-qemu64: true
Upstream PR: https://github.com/kubevirt/ssp-operator/pull/80
Verified with kubevirt-ssp-operator-container-v2.6.0-32
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 2.6.0 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-2021:0799