Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-59598

VMI ctrl repeated patches virt-launcher pod when VM has multiple SR-IOV NICs

XMLWordPrintable

    • Quality / Stability / Reliability
    • 0.42
    • False
    • Hide

      None

      Show
      None
    • False
    • CNV v4.99.0.rhel9-2292, CNV v4.19.0.rhel9-126
    • 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.19

      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

              omisan@redhat.com Orel Misan
              omisan@redhat.com Orel Misan
              Yossi Segev Yossi Segev
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: