Confirmed with the latest payload, the issue has fixed:
[root@dhcp-140-138 ~]# oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.1.0-0.nightly-2020-01-21-160338 True False 42m Cluster version is 4.1.0-0.nightly-2020-01-21-160338
[root@dhcp-140-138 ~]# oc get cm -n kube-system
NAME DATA AGE
bootstrap 1 58m
cluster-config-v1 1 63m
extension-apiserver-authentication 6 63m
kube-controller-manager 0 62m
root-ca 1 63m
[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 59m
cluster-config-v1 1 63m
extension-apiserver-authentication 6 63m
kube-controller-manager 0 3s
root-ca 1 63m
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:0399