Bug 1880463 - [OCP 4.5] kube-apiserver unresponsive - context canceled errors
Summary: [OCP 4.5] kube-apiserver unresponsive - context canceled errors
Keywords:
Status: CLOSED DUPLICATE of bug 1883589
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.7.0
Assignee: Lukasz Szaszkiewicz
QA Contact: Ke Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-18 15:45 UTC by Mario Abajo
Modified: 2020-10-08 11:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-08 11:00:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 6 Stefan Schimanski 2020-10-02 09:43:07 UTC
The message
 
  killing connection/stream because serving request timed out and response had been started

means that we see timeouts of requests (after 60s) and the response has partly be written. This is not the typical timeout due to slow etcd as then the response is usually not started yet. This looks more like outgoing network issues, i.e. the apiserver cannot send back the data to the client in time. I see something about Istio is known to reconfigure networking quite a bit. The chance is high that the issue is on that side.

Note: we are working improving the error output "apiserver panic'd ...." as this is technically a panic, but a gracefully handled one. It is expected in this situation and is not critical for the apiserver, compare https://github.com/kubernetes/kubernetes/pull/95002.


Note You need to log in before you can comment on or make changes to this bug.