After the cluster is up for just a short time the number of revisions of the kube-scheduler is very high. After 20m, we are near revision 100.
Due to unstable map ordering https://github.com/openshift/cluster-kube-scheduler-operator/blob/master/pkg/operator/target_config_reconciler_v311_00.go#L151
Bug went in on https://github.com/openshift/cluster-kube-scheduler-operator/pull/72 about 21 hours ago
PR - https://github.com/openshift/cluster-kube-scheduler-operator/pull/99
(In reply to Seth Jennings from comment #2)
> Bug went in on
> https://github.com/openshift/cluster-kube-scheduler-operator/pull/72 about
> 21 hours ago
after 28h, there's no a lot of revisions of cm as below, is this good enough for pushing the bug to VERIFIED?
[nathan@dhcp-140-199 0422]$ oc get cm
NAME DATA AGE
config 1 28h
config-1 1 28h
config-2 1 28h
config-3 1 28h
kube-scheduler-pod 3 28h
kube-scheduler-pod-1 3 28h
kube-scheduler-pod-2 3 28h
kube-scheduler-pod-3 3 28h
revision-status-1 2 28h
revision-status-2 2 28h
revision-status-3 2 28h
scheduler-kubeconfig 1 28h
scheduler-kubeconfig-1 1 28h
scheduler-kubeconfig-2 1 28h
scheduler-kubeconfig-3 1 28h
serviceaccount-ca 1 28h
serviceaccount-ca-1 1 28h
serviceaccount-ca-2 1 28h
serviceaccount-ca-3 1 28h
[nathan@dhcp-140-199 0422]$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.1.0-0.nightly-2019-04-20-175514 True False 22h Cluster version is 4.1.0-0.nightly-2019-04-20-175514
Yes, that is the expected result.
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.