Bug 2091157
| Summary: | [4.10z] Completed pods in Openshift cluster not releasing IP addresses and results in err: range is full unless manually deleted | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Tim Rozet <trozet> |
| Component: | Networking | Assignee: | Tim Rozet <trozet> |
| Networking sub component: | ovn-kubernetes | QA Contact: | zhaozhanqi <zzhao> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | urgent | ||
| Priority: | urgent | CC: | ableisch, alosingh, anusaxen, bpickard, bsmitley, danw, davlewis, fgleizes, gmeghnag, hyupark, jkaur, mdeore, rbolling, rbrattai, skudupud, swasthan, trozet, vpickard, zzhao |
| Version: | 4.8 | Keywords: | FastFix |
| Target Milestone: | --- | ||
| Target Release: | 4.10.z | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 2026461 | Environment: | |
| Last Closed: | 2022-07-07 11:39:56 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: | 2026461 | ||
| Bug Blocks: | |||
|
Comment 7
zhaozhanqi
2022-06-30 06:02:17 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 (OpenShift Container Platform 4.10.21 bug fix update), 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-2022:5428 Hi - As requested by Martin Kennelly. My customer is running a disconnected v4.10.22 cluster (OCP on OSP) using ovn-kubernetes and we are still seeing this bug. Example pod error message: addLogicalPort failed for <<namespaces>>/<<pod>>: failed to assign pod address for pod <<pod>> no node: worker-node, err: range is full. The other way to resolve this is to either keep deleting the pod until it hits a node it can come up on, or removing all Completed / Error pods on the cluster. If this could be re-looked at I would be most grateful. Thanks - Dave The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |