Bug 1939226 - kube-apiserver readiness probe appears to be hitting /healthz, not /readyz
Summary: kube-apiserver readiness probe appears to be hitting /healthz, not /readyz
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: David Eads
QA Contact: Ke Wang
Depends On:
Blocks: 1945925 1945926 1945927
TreeView+ depends on / blocked
Reported: 2021-03-15 18:49 UTC by Elana Hashman
Modified: 2021-07-27 22:53 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-07-27 22:53:18 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-kube-apiserver-operator pull 1065 0 None open bug 1939226: make kube-apiserver readiness checks, check readyz 2021-03-15 19:37:08 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:53:42 UTC

Description Elana Hashman 2021-03-15 18:49:49 UTC
Description of problem:

When looking at logs of an unhealthy API server, I noticed it appears to be hitting /healthz instead of /readyz for readiness probes.

Mar 15 03:01:36.711435 ip-10-0-146-200 hyperkube[1442]: I0315 03:01:36.711411    1442 prober.go:117] Readiness probe for "kube-apiserver-ip-10-0-146-200.us-west-1.compute.internal_openshift-kube-apiserver(22bd459e-677c-40ce-a715-9a263b663b2b):kube-apiserver" failed (failure): Get "": net/http: request canceled (Client.Timeout exceeded while awaiting headers)

See also must-gather here: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.8/1371290082278903808/artifacts/e2e-aws/

Version-Release number of selected component (if applicable): 4.8?

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 2 David Eads 2021-03-16 19:27:34 UTC
readyz isn't used to maintain the kube-apiserver service endpoints (it directly writes), but it does impact the metrics gathering

Comment 4 Xingxing Xia 2021-04-07 10:27:59 UTC
Verified in 4.8.0-0.nightly-2021-04-06-162113 per result in https://bugzilla.redhat.com/show_bug.cgi?id=1939227#c5 .

Comment 7 errata-xmlrpc 2021-07-27 22:53:18 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security 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.


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