Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1553297 - [3.7] various auto-egress IP problems
[3.7] various auto-egress IP problems
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking (Show other bugs)
3.7.1
Unspecified Unspecified
high Severity high
: ---
: 3.7.z
Assigned To: Ben Bennett
Meng Bo
:
Depends On: 1551028
Blocks:
  Show dependency treegraph
 
Reported: 2018-03-08 11:07 EST by Dan Winship
Modified: 2018-04-05 05:40 EDT (History)
5 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-04-05 05:39:53 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
Origin (Github) 18808 None None None 2018-03-08 11:07 EST
Github openshift/ose/pull/1106 None None None 2018-03-15 10:51 EDT
Red Hat Product Errata RHBA-2018:0636 None None None 2018-04-05 05:40 EDT

  None (edit)
Comment 1 Dan Winship 2018-03-08 11:08:52 EST
https://github.com/openshift/ose/pull/1106
Comment 4 Meng Bo 2018-03-20 22:14:44 EDT
Tested on v3.7.39 issue has been fixed.
Comment 8 errata-xmlrpc 2018-04-05 05:39:53 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/RHBA-2018:0636

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