Bug 1779938
Summary: | GCP: Kube API started failing ... request canceled (Client.Timeout exceeded while awaiting headers) | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | W. Trevor King <wking> |
Component: | kube-apiserver | Assignee: | Stefan Schimanski <sttts> |
Status: | CLOSED DUPLICATE | QA Contact: | Ke Wang <kewang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.3.0 | CC: | aos-bugs, mfojtik, nagrawal, xxia |
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-06-18 10:03:16 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
2019-12-05 03:52:10 UTC
Bumping-up severity as 10% of tests are failing with this error. https://github.com/openshift/machine-config-operator/pull/1670 might help. We will revisit this BZ when the PR merged. https://github.com/openshift/machine-config-operator/pull/1670 merged. Moving to modified. This seems to be common problem, from below searching results, there are 11 bugs related to this, and matched 16.52% of failing runs and 12.26% of jobs, we don't see a significant decline. I don't think it was resolved by the PR https://github.com/openshift/machine-config-operator/pull/1670, so assign it back. https://search.apps.build01.ci.devcluster.openshift.com/?search=Client.Timeout+exceeded+while+awaiting+headers&maxAge=12h&context=1&type=all&name=&maxMatches=5&maxBytes=20971520&groupBy=job We are on this topic, but it does not block 4.5 in the current form. Moving to 4.6. Note that many of the runs in the search in #12 are not GCP related. This issue was about GCP only. We are tracking these in #1845410. *** This bug has been marked as a duplicate of bug 1845410 *** |