Description of problem: Too many error from scheduler pod :Failed to list *v1.ConfigMap: configmaps "extension-apiserver-authentication" is forbidden: User "system:kube-scheduler" cannot list resource "configmaps" in API group "" in the namespace "kube-system" Version-Release number of selected component (if applicable): 4.3.0-0.nightly-2019-11-28-004553 How reproducible: Always Steps to Reproduce: 1. Check logs from openshift-kube-scheduler pod. `oc logs -f po/openshift-kube-scheduler-ip-10-0-55-254.ap-northeast-1.compute.internal` Actual results: 1. Too many errors from the pod: E1129 08:09:42.181496 1 reflector.go:123] k8s.io/apiserver/pkg/server/dynamiccertificates/configmap_cafile_content.go:209: Failed to list *v1.ConfigMap: configmaps "extension-apiserver-authentication" is forbidden: User "system:kube-scheduler" cannot list resource "configmaps" in API group "" in the namespace "kube-system" E1129 08:09:42.411249 1 reflector.go:123] k8s.io/apiserver/pkg/server/dynamiccertificates/configmap_cafile_content.go:209: Failed to list *v1.ConfigMap: configmaps "extension-apiserver-authentication" is forbidden: User "system:kube-scheduler" cannot list resource "configmaps" in API group "" in the namespace "kube-system" Expected results: No such error. Additional info:
*** Bug 1769931 has been marked as a duplicate of this bug. ***
It got fixed on 4.4 with the rebase. QA pls verify this so we can ship a backport in https://bugzilla.redhat.com/show_bug.cgi?id=1790481
Confirmed with the payload: 4.4.0-0.nightly-2020-01-14-135405, can't reproduce the issue now: [root@dhcp-140-138 ~]# oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.4.0-0.nightly-2020-01-14-135405 True False 67m Cluster version is 4.4.0-0.nightly-2020-01-14-135405
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