we need to move https://github.com/kubernetes/kubernetes/pull/88763 so that errors like configmap_cafile_content.go:102] unable to load initial CA bundle for: "client-ca::kube-system::extension-apiserver-authentication::client-ca-file" due to: configmap "extension-apiserver-authentication" not found will not be printed at the server startup.
Xingxing I think that in order to to verify just make sure that the server doesn't print "configmap_cafile_content.go:102] unable to load initial CA bundle for: "client-ca::kube-system::extension-apiserver-authentication::client-ca-file" due to: configmap "extension-apiserver-authentication" not found" at the startup.
@Lukasz, I checked the PR has been merged into build 4.4.0-0.nightly-2020-03-26-041820, but failed to verify, see below, $ oc adm release info --commits registry.svc.ci.openshift.org/ocp/release:4.4.0-0.nightly-2020-03-26-041820 | grep ose hyperkube https://github.com/openshift/ose 1140645a27b9f11717f70b6b74efb1b09ca7d089 $ git log --date local --pretty="%h %an %cd - %s" 1140645 | grep '#24677' b80bcf408b OpenShift Merge Robot Sat Mar 14 15:16:54 2020 - Merge pull request #24677 from p0lyn0mial/pick-88763-clean-up-dynamiccert-pkg-4.4 $ master=$(oc get nodes | grep master | head -1 | cut -d " " -f1) $ oc debug node/$master ... sh-4.2# chroot /host sh-4.4# cd /var/log/pods sh-4.4# grep -nr 'unable to load initial CA bundle for' openshift* openshift-apiserver_apiserver-688558b7ff-bthkn_fabfe150-5354-43ae-beb3-5ceea5ddc2df/openshift-apiserver/0.log:2:2020-03-27T07:54:36.857271015+00:00 stderr F W0327 07:54:36.857146 1 configmap_cafile_content.go:102] unable to load initial CA bundle for: "client-ca::kube-system::extension-apiserver-authentication::client-ca-file" due to: configmap "extension-apiserver-authentication" not found openshift-apiserver_apiserver-688558b7ff-bthkn_fabfe150-5354-43ae-beb3-5ceea5ddc2df/openshift-apiserver/0.log:3:2020-03-27T07:54:36.857324431+00:00 stderr F W0327 07:54:36.857295 1 configmap_cafile_content.go:102] unable to load initial CA bundle for: "client-ca::kube-system::extension-apiserver-authentication::requestheader-client-ca-file" due to: configmap "extension-apiserver-authentication" not found openshift-insights_insights-operator-fbd76b678-v8d47_d3e9dbc2-5795-4438-a19b-3f1ccbf86a9a/operator/0.log:9:2020-03-27T01:33:54.314437640+00:00 stderr F W0327 01:33:54.303657 1 configmap_cafile_content.go:102] unable to load initial CA bundle for: "client-ca::kube-system::extension-apiserver-authentication::client-ca-file" due to: configmap "extension-apiserver-authentication" not found openshift-insights_insights-operator-fbd76b678-v8d47_d3e9dbc2-5795-4438-a19b-3f1ccbf86a9a/operator/0.log:10:2020-03-27T01:33:54.314437640+00:00 stderr F W0327 01:33:54.303826 1 configmap_cafile_content.go:102] unable to load initial CA bundle for: "client-ca::kube-system::extension-apiserver-authentication::requestheader-client-ca-file" due to: configmap "extension-apiserver-authentication" not found openshift-insights_insights-operator-fbd76b678-v8d47_d3e9dbc2-5795-4438-a19b-3f1ccbf86a9a/operator/1.log:9:2020-03-27T01:38:57.456065500+00:00 stderr F W0327 01:38:57.456025 1 configmap_cafile_content.go:102] unable to load initial CA bundle for: "client-ca::kube-system::extension-apiserver-authentication::client-ca-file" due to: configmap "extension-apiserver-authentication" not found openshift-insights_insights-operator-fbd76b678-v8d47_d3e9dbc2-5795-4438-a19b-3f1ccbf86a9a/operator/1.log:10:2020-03-27T01:38:57.456222208+00:00 stderr F W0327 01:38:57.456201 1 configmap_cafile_content.go:102] unable to load initial CA bundle for: "client-ca::kube-system::extension-apiserver-authentication::requestheader-client-ca-file" due to: configmap "extension-apiserver-authentication" not found From above, we can see the fix does not work as expected.
@Ke the fix only improved "kube-apiserver" not "openshift-apiserver". Could you check the former?
@Lukasz, I checked again, sh-4.4# grep -nr 'unable to load initial CA bundle for' openshift-kube-apiserver* sh-4.4# Nothing found for "kube-apiserver". So there should be one bug to track the "openshift-apiserver"?
@Ke yeah, "openshift-apiserver" will be tracked in a seperate issue (I'm going to add one"). Thanks for pointing that out.
@Ke OAS will be tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1814207
@Lukasz, thank you for your reminder, will verify it later.
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, 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:0581