Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1553294 - [3.9] various auto-egress IP problems
[3.9] various auto-egress IP problems
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking (Show other bugs)
3.9.0
Unspecified Unspecified
high Severity high
: ---
: 3.9.0
Assigned To: Ben Bennett
Meng Bo
:
Depends On: 1551028 1553296
Blocks:
  Show dependency treegraph
 
Reported: 2018-03-08 11:04 EST by Dan Winship
Modified: 2018-06-27 14:02 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
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.
Story Points: ---
Clone Of: 1551028
Environment:
Last Closed: 2018-06-27 14:01:34 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2013 None None None 2018-06-27 14:02 EDT

  None (edit)
Comment 1 Dan Winship 2018-03-08 11:05:37 EST
https://github.com/openshift/origin/pull/18861
Comment 2 Ben Bennett 2018-04-13 10:23:06 EDT
Sorry, this went out with 3.9.0 and was backported.
Comment 3 Meng Bo 2018-05-02 04:22:08 EDT
Tested on build v3.9.27, the egress ip issues have been fixed.
Comment 5 errata-xmlrpc 2018-06-27 14:01:34 EDT
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

Note You need to log in before you can comment on or make changes to this bug.