Bug 1939542 - p&f: probes should not get 429s [NEEDINFO]
Summary: p&f: probes should not get 429s
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.5.z
Assignee: Abu Kashem
QA Contact: Ke Wang
Whiteboard: LifecycleStale
Depends On: 1939541
TreeView+ depends on / blocked
Reported: 2021-03-16 15:20 UTC by Abu Kashem
Modified: 2021-08-03 15:22 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1939541
Last Closed: 2021-08-03 15:22:12 UTC
Target Upstream Version:
mfojtik: needinfo?

Attachments (Terms of Use)

Description Abu Kashem 2021-03-16 15:20:57 UTC
+++ This bug was initially created as a clone of Bug #1939541 +++

+++ This bug was initially created as a clone of Bug #1939537 +++

+++ This bug was initially created as a clone of Bug #1937916 +++

Messages like

Get "": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

appear to be produced by kubelet even when the pod is able to communicate with itself. This causes outage of system services as they are not deemed healthy:

	Liveness probe failed: HTTP probe failed with statuscode: 429

More details in https://coreos.slack.com/archives/C01RLRP2F9N

--- Additional comment from David Eads on 2021-03-11 18:29:01 UTC ---

I've opened https://github.com/openshift/cluster-kube-apiserver-operator/pull/1060 as a possibility, but I'd like a review from Abu

Comment 1 Michal Fojtik 2021-04-15 15:48:24 UTC
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.

Comment 2 Vikas Laad 2021-08-03 15:22:12 UTC
OCP 4.5 is out of support now, there will not be any more releases for 4.5

Please see lifecycle policy
https://access.redhat.com/support/policy/updates/openshift for supported

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