Confirmed with payload: 4.3.0-0.nightly-2019-12-11-204310, the issue has fixed: [root@dhcp-140-138 ~]# oc get cm -n kube-system NAME DATA AGE bootstrap 1 95m cluster-config-v1 1 104m extension-apiserver-authentication 6 104m kube-controller-manager 0 104m root-ca 1 104m [root@dhcp-140-138 ~]# oc delete cm/kube-controller-manager -n kube-system configmap "kube-controller-manager" deleted [root@dhcp-140-138 ~]# oc get cm -n kube-system NAME DATA AGE bootstrap 1 96m cluster-config-v1 1 104m extension-apiserver-authentication 6 104m kube-controller-manager 0 2s root-ca 1 104m
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:0062