Bug 1718542
| Summary: | [3.11] Random outages with egressIP | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Dan Winship <danw> | |
| Component: | Networking | Assignee: | Dan Winship <danw> | |
| Status: | CLOSED ERRATA | QA Contact: | zhaozhanqi <zzhao> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 3.11.0 | CC: | aos-bugs, jack.ottofaro, joboyer, openshift-bugs-escalate, sburke, shiywang, travi, zzhao | |
| Target Milestone: | --- | Keywords: | Reopened | |
| Target Release: | 3.11.z | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause: If a pod using an egress IP tries to contact an external host that is not responding, the egress IP monitoring code may mistakenly interpret that as meaning that the node hosting the egress IP is not responding.
Consequence: High-availability egress IPs might get switched from one node to another spuriously.
Fix: The monitoring code now distinguishes the case of "egress node not responding" from "final destination not responding"
Result: High-availability egress IPs will not be switched between nodes unnecessarily.
|
Story Points: | --- | |
| Clone Of: | 1717639 | |||
| : | 1728342 (view as bug list) | Environment: | ||
| Last Closed: | 2019-07-09 17:58:21 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: | 1717639 | |||
| Bug Blocks: | 1728342 | |||
|
Comment 3
Sean Burke
2019-06-25 17:22: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-2019:1605 Ravi Trivedi yeah, if they can provide the details commands, that's more better. since I cannot reproduce this issue on 3.11.117 using the above steps. thanks. This fix wasn't in 3.11.117; it was committed just after that version was tagged. So it didn't make the latest errata. I'm not sure how it ended up being listed as fixed there. (It will be in the next errata.) close this one in favor of https://bugzilla.redhat.com/show_bug.cgi?id=1728342 |