Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-49857

[release-4.18] UDN - Egress L2 VMs IPv4 traffic over previous node after live migration

XMLWordPrintable

    • None
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when you finished the live migration for a kubevirt virtual machine (VM) that uses the Layer 2 topology, an old node still transmits IPv4 egress traffic to the virtual machine. With this release, the OVN-Kubernetes plugin updates the gateway MAC address for a kubevirt virtual machine (VM) during the live migration process so that this issue no longer occurs. (link:https://issues.redhat.com/browse/OCPBUGS-49857[*OCPBUGS-49857*])
      Show
      * Previously, when you finished the live migration for a kubevirt virtual machine (VM) that uses the Layer 2 topology, an old node still transmits IPv4 egress traffic to the virtual machine. With this release, the OVN-Kubernetes plugin updates the gateway MAC address for a kubevirt virtual machine (VM) during the live migration process so that this issue no longer occurs. (link: https://issues.redhat.com/browse/OCPBUGS-49857 [* OCPBUGS-49857 *])
    • Bug Fix
    • Done

      Description of problem:

       

      After kubevirt vm live migration, VM egress traffic still going over the previous node wher the VM was running before live migration.
      

       

      Version-Release number of selected component (if applicable): 4.19

      How reproducible: Always

      Steps to Reproduce:

       

      1. Create a vm with, primary UDN, l2 topology and ipv4
      2. Send egress traffic
      3 . Live migrate the VM
      4. Send egress traffic  
      

      Actual results:

      IPv4 egress traffic goes over the node was running before live migration

       

      Expected results:

      IPv4 Egress traffic should go over the node where the VM is running after the live migration

       

      Additional info:

      The problem is related to VM ipv4 neighbors cache not being updated, to fix this a GARP should be send by ovn-kubernetes to update that cache after live migration.

              ellorent Felix Enrique Llorente Pastora
              ellorent Felix Enrique Llorente Pastora
              Anat Wax Anat Wax
              Darragh Fitzmaurice Darragh Fitzmaurice
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: