|Summary:||[3.9] various auto-egress IP problems|
|Product:||OpenShift Container Platform||Reporter:||Dan Winship <danw>|
|Component:||Networking||Assignee:||Ben Bennett <bbennett>|
|Status:||CLOSED ERRATA||QA Contact:||Meng Bo <bmeng>|
|Version:||3.9.0||CC:||aos-bugs, bbennett, bmeng, dzhukous|
|Fixed In Version:||Doc Type:||Bug Fix|
Cause: Bugs Consequence: When using the "static per-project egress IPs" feature, egress IPs may stop working in some circumstances if an egress IP is moved from one project to another, or from one node to another. Additionally, if the same egress IP is assigned to two different projects, or two different nodes, then it may not work correctly even after the duplicate assignment is removed. Fix: Bugs fixed Result: Static per-project egress IPs should work more reliably.
|Last Closed:||2018-06-27 18:01:34 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:||1551028, 1553296|
Comment 2 Ben Bennett 2018-04-13 14:23:06 UTC
Sorry, this went out with 3.9.0 and was backported.
Comment 3 Meng Bo 2018-05-02 08:22:08 UTC
Tested on build v3.9.27, the egress ip issues have been fixed.
Comment 5 errata-xmlrpc 2018-06-27 18:01:34 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/RHSA-2018:2013