Bug 1734009
| Summary: | [3.11 backport] Synchronization firewall rules takes up to 90min | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Casey Callendrello <cdc> |
| Component: | Networking | Assignee: | Casey Callendrello <cdc> |
| Networking sub component: | openshift-sdn | QA Contact: | zhaozhanqi <zzhao> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | urgent | CC: | aos-bugs, cdc, clichybi, dcbw, emahoney, grodrigu, huirwang, jack.ottofaro, nstielau, openshift-bugs-escalate, piqin, rbinkhor, rhowe, scuppett, simon.gerber, sperezto, sponnaga, tobias.brunner, vlaad, zzhao |
| Version: | 3.11.0 | ||
| Target Milestone: | --- | ||
| Target Release: | 3.11.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: The unidling proxy caused iptables lock contention with the service proxy.
Consequence: Clusters with large numbers of services and unidled services could see long times in applying endpoint changes to cluster ips.
Fix: Access to iptables is better coordinated.
|
Story Points: | --- |
| Clone Of: | 1699341 | Environment: | |
| Last Closed: | 2019-09-24 08:08:08 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: | 1699341 | ||
| Bug Blocks: | |||
|
Comment 1
Ryan Howe
2019-07-31 16:47:37 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:2816 *** Bug 1590589 has been marked as a duplicate of this bug. *** *** Bug 1712494 has been marked as a duplicate of this bug. *** |