Bug 1553296
Summary: | [3.8] various auto-egress IP problems | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Dan Winship <danw> |
Component: | Networking | Assignee: | Dan Winship <danw> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Meng Bo <bmeng> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.8.0 | CC: | aos-bugs, bbennett, bmeng, dzhukous, eparis |
Target Milestone: | --- | ||
Target Release: | 3.8.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
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-08-23 14:15:52 UTC | Type: | Bug |
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: | 1551028 | ||
Bug Blocks: | 1553294 |
Comment 1
Dan Winship
2018-03-08 16:10:26 UTC
Dan did exactly the right thing with this bug, and I am going to do something terrible. This bug belongs on a 3.8.z list, however there is no 3.8.z target release. I am adding 'target release' == 3.10 to get it off of the 3.9 release blocking lists. Once we stop looking at 3.8/3.9 blockers this bug should return to targeting 3.8. I'm so sorry. I feel dirty. closing old fixed 3.8 bugs |