-
Bug
-
Resolution: Unresolved
-
Critical
-
4.19
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.
- clones
-
OCPBUGS-49337 [4.19] UDN - Egress L2 VMs IPv4 traffic over previous node after live migration
-
- ON_QA
-
- depends on
-
OCPBUGS-49337 [4.19] UDN - Egress L2 VMs IPv4 traffic over previous node after live migration
-
- ON_QA
-
- links to
-
RHSA-2024:6122 OpenShift Container Platform 4.18.z security update