shows that KS wasn't able to run because it failed looking up in-cluster configuration due to insufficient permissions (configmaps "extension-apiserver-authentication" is forbidden: User "system:kube-scheduler" cannot get resource "configmaps" in API group "" in the namespace "kube-system")
the audit logs revealed it communicated "10-0-176-71" which wasn't fully running at that time 03:59:06. There is a high chance that the request was rejected because the RBAC controller wasn't fully synchronised.
 - https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade/1305692415100719104/artifacts/e2e-aws-upgrade/pods/openshift-kube-scheduler_openshift-kube-scheduler-ip-10-0-176-71.ec2.internal_kube-scheduler.log
 - https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade/1305692415100719104
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.