Bug 1762235 - [3.11 backport] Duplicated IPs on InfraNodes using automatic egress IP
Summary: [3.11 backport] Duplicated IPs on InfraNodes using automatic egress IP
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.11.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 3.11.z
Assignee: Dan Winship
QA Contact: huirwang
URL:
Whiteboard:
Depends On: 1753216
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-16 09:45 UTC by huirwang
Modified: 2024-03-25 15:28 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: When the SDN pod was restarted on a node, it did not clean up any old Egress IPs. Consequence: If the set of Egress IPs assigned to a node changed while the SDN pod was not running (eg, because multiple services on the node were restarted at the same time) then the node might continue to claim that it owned the Egress IP even after the IP had been assigned to another node, causing traffic to that IP to be delivered to the wrong node and be lost. Fix: The SDN pod now cleans up stale Egress IPs at startup. Result: Nodes should not fight over ownership of Egress IPs.
Clone Of: 1753216
Environment:
Last Closed: 2020-01-14 05:31:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 24161 0 'None' closed Bug 1762235: [3.11] Clean up egress IPs on startup 2021-01-26 13:02:20 UTC
Red Hat Knowledge Base (Solution) 4490291 0 None None None 2020-02-27 05:15:08 UTC
Red Hat Product Errata RHBA-2020:0017 0 None None None 2020-01-14 05:31:39 UTC

Comment 27 errata-xmlrpc 2020-01-14 05:31:27 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0017
Note You need to log in before you can comment on or make changes to this bug.