-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
CLOSED
-
-
-
Important
-
No
Description of problem: on AMD nodes, we see these cpu-model labels
cpu-model-migration.node.kubevirt.io/EPYC-Rome=true
cpu-model-migration.node.kubevirt.io/Nehalem=true
cpu-model-migration.node.kubevirt.io/Nehalem-IBRS=true
cpu-model-migration.node.kubevirt.io/Opteron_G1=true
cpu-model-migration.node.kubevirt.io/Opteron_G2=true
cpu-model-migration.node.kubevirt.io/Penryn=true
cpu-model-migration.node.kubevirt.io/SandyBridge=true
cpu-model-migration.node.kubevirt.io/SandyBridge-IBRS=true
cpu-model-migration.node.kubevirt.io/Westmere=true
cpu-model-migration.node.kubevirt.io/Westmere-IBRS=true
Here only EPYC-Rome and Opteron_G1/2 are AMD CPU models
Version-Release number of selected component (if applicable):
4.13.0 (where found, might be same on older versions)
How reproducible:
100%
Steps to Reproduce:
1. oc describe node <node-name>
2.
3.
Actual results:
Intel CPU models present on AMD CPU nodes
Expected results:
node labels has only relevant cpu models
Additional info:
This wrong labeling causes issues with nested virtualization (windows 10/11 vm can't run wsl2 internal vm) when vm is assigned with wrong cpu model