-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.14.z, 4.15, 4.16, 4.17.z, 4.18.z
This is a clone of issue OCPBUGS-42303. The following is the description of the original issue:
—
Description of problem:
After rebooting an egressIP assignee node (let's say node A) the egressIP is correctly moved to a different node if available (node B), but when the ovnkube-node starts on node A it sends a couple of Gratuitos ARP requests for that egressIP no more assigned to it.
Version-Release number of selected component (if applicable):
4.15 (also reproduced in 4.16.11)
How reproducible:
100% Always
Steps to Reproduce:
1. Configure egressIP and 2 assignable nodes
2. Reboot the assignee node.
3. Verify the egressIP moved to another node, and when ovnkube-node starts on the previous assignee it sends a couple of GARP request for the egressIP assigned to another node.
Actual results:
The previous egressIP assignee node sends GARPs for an egressIP not assigned to it causing the neighbors in the network to set the wrong MAC address in the ARP table for the egressIP.
Expected results:
The previous egressIP assignee node should not send GARPs for an egressIP not assigned to it.
Additional info:
This behavior is particularly problematic when in the underlying infrastructure is enabled a mechanisms for caching ARP.
- clones
-
OCPBUGS-62273 [release-4.20] egressIP GARP sent by incorrect node after reboot
-
- POST
-
- depends on
-
OCPBUGS-62671 [release-4.18] egressIP GARP sent by incorrect node after reboot
-
- New
-
- is cloned by
-
OCPBUGS-62671 [release-4.18] egressIP GARP sent by incorrect node after reboot
-
- New
-
- is depended on by
-
OCPBUGS-62273 [release-4.20] egressIP GARP sent by incorrect node after reboot
-
- POST
-
- links to