Bug 1762235

Summary: [3.11 backport] Duplicated IPs on InfraNodes using automatic egress IP
Product: OpenShift Container Platform Reporter: huirwang
Component: NetworkingAssignee: Dan Winship <danw>
Networking sub component: openshift-sdn QA Contact: huirwang
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: aghadge, aivaraslaimikis, ajohn, bbennett, blima, danw, huirwang, jnordell, natanfranghieru, palonsor, rhowe, xtian, zzhao
Version: 3.11.0Keywords: NeedsTestCase
Target Milestone: ---   
Target Release: 3.11.z   
Hardware: x86_64   
OS: Linux   
Whiteboard:
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.
 Story Points: ---
Clone Of: 1753216 Environment:
Last Closed: 2020-01-14 05:31:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1753216    
Bug Blocks:    

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