Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1882446

Summary: kube-apiserver logs pre-/readyz message infinitely
Product: OpenShift Container Platform Reporter: Stefan Schimanski <sttts>
Component: kube-apiserverAssignee: Stefan Schimanski <sttts>
Status: CLOSED ERRATA QA Contact: Ke Wang <kewang>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.6CC: aos-bugs, mfojtik, 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-10-27 16:45:08 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 Stefan Schimanski 2020-09-24 15:07:04 UTC
Even after readyz is green, kube-apiserver keeps logging pre-readyz messages:

I0922 15:30:15.741044      18 patch_genericapiserver.go:119] Loopback request to "/apis/apiregistration.k8s.io/v1/apiservices" (user agent "kube-apiserver/v1.19.0 (linux/amd64) kubernetes/d55f10b") before server is ready. This client probably does not watch /readyz and might get inconsistent answers.

Comment 2 Ke Wang 2020-09-27 07:43:44 UTC
$ oc adm release info --commits registry.svc.ci.openshift.org/ocp/release:4.6.0-0.nightly-2020-09-26-202331 | grep hyperkube
  hyperkube       https://github.com/openshift/kubernetes     e465e6672b7753d15336f3be1434c03ed8916a41

$  git log --date local --pretty="%h %an %cd - %s" e465e667 | grep ' #374 '
31bf081b178 OpenShift Merge Robot Fri Sep 25 17:34:21 2020 - Merge pull request #374 from sttts/sttts-fix-readyz-warning

From kube-apiserver-check-endpoints log, the kube-apiserver was ready for serving at 05:42:39,
...
I0927 05:42:39.727943       1 base_controller.go:109] Starting #1 worker of check-endpoints controller ...
I0927 05:42:39.728186       1 connection_checker.go:110] Started connectivity check kube-apiserver-kewang27dr1-btdxn-m-0.c.openshift-qe.internal-to-openshift-apiserver-endpoint-kewang27dr1-btdxn-m-0.c.openshift-qe.internal.
I0927 05:42:39.728309       1 connection_checker.go:110] Started connectivity check kube-apiserver-kewang27dr1-btdxn-m-0.c.openshift-qe.internal-to-etcd-server-kewang27dr1-btdxn-m-1.c.openshift-qe.internal.


From kube-apiserver log, the last time the log appeared at 05:42:38,
...
kube-apiserver.log:I0927 05:42:38.589585      18 patch_genericapiserver.go:119] Loopback request to "/apis/rbac.authorization.k8s.io/v1/namespaces/kube-system/rolebindings/system:controller:token-cleaner" (user agent "kube-apiserver/v1.19.0+e465e66 (linux/amd64) kubernetes/e465e66") before server is ready. This client probably does not watch /readyz and might get inconsistent answers.
kube-apiserver.log:I0927 05:42:38.591676      18 patch_genericapiserver.go:119] Loopback request to "/apis/rbac.authorization.k8s.io/v1/namespaces/kube-public/rolebindings/system:controller:bootstrap-signer" (user agent "kube-apiserver/v1.19.0+e465e66 (linux/amd64) kubernetes/e465e66") before server is ready. This client probably does not watch /readyz and might get inconsistent answers.

The pre-readyz messages won't be seen after the kube-apiserver readiness as expected, so move the bug verified.

Comment 5 errata-xmlrpc 2020-10-27 16:45:08 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 (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4196