Bug 1822417
Summary: | "bind: address already in use" masked by usage spew in pod logs | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | W. Trevor King <wking> |
Component: | kube-apiserver | Assignee: | David Eads <deads> |
Status: | CLOSED DUPLICATE | QA Contact: | Xingxing Xia <xxia> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 4.5 | CC: | aos-bugs, mfojtik, sttts |
Target Milestone: | --- | ||
Target Release: | 4.6.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-05-20 14:54:04 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: |
Description
W. Trevor King
2020-04-08 23:54:15 UTC
Seen again on [1], where it's now fatal for 4.5 update CI (via bug 1828427). Should I split off a separate bug for the "bind: address already in use" crashlooping, so this one stays focused on log spew? [1]: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade/27314 Seems like this got a 'SilenceUsage' upstream in [1]. Not sure when that will land in OpenShift, but that should address the usage-spew portion of this. [1]: https://github.com/kubernetes/kubernetes/pull/90297 fixed by https://github.com/openshift/origin/pull/24945 *** This bug has been marked as a duplicate of bug 1831533 *** Looks like bug 1831533 addressed the usage spew. Did we have a separate ticket open for the bind contention that was being masked? |