-
Bug
-
Resolution: Done-Errata
-
Major
-
CNV v4.18.0
-
Quality / Stability / Reliability
-
0.42
-
False
-
-
False
-
CNV v4.18.3.rhel9-3
-
-
Important
-
None
Description of problem:
When a VM has an SR-IOV NIC, the VMI controller adds the `kubevirt.io/network-info` annotation to the virt-launcher pod. This annotation's value is a JSON array derived from the Multus network status annotation (`k8s.v1.cni.cncf.io/network-status`). When there are multiple SR-IOV NICs, the order of the JSON array keeps changing - thus the VMI controller repeatedly patches the pod.
Version-Release number of selected component (if applicable):
4.18
How reproducible:
100%
Steps to Reproduce:
1. Create a VM with multiple SR-IOV NICs (see example in the upstream issue).
Actual results:
VMI controller patches the pod whenever the JSON array element order changes
Expected results:
VMI controller will only patch the pod when required
Additional info:
First reported in: https://github.com/kubevirt/kubevirt/issues/14442
- clones
-
CNV-59598 VMI ctrl repeated patches virt-launcher pod when VM has multiple SR-IOV NICs
-
- Closed
-
- links to
-
RHEA-2025:149631 OpenShift Virtualization 4.18.5 Images