Bug 1699447
| Summary: | kube-scheduler-operator causing very frequent revision bumps triggered by "configmap/kube-scheduler-pod has changed" | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Seth Jennings <sjenning> |
| Component: | Node | Assignee: | ravig <rgudimet> |
| Status: | CLOSED ERRATA | QA Contact: | Weinan Liu <weinliu> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.1.0 | CC: | aos-bugs, jokerman, mmccomas, wking |
| Target Milestone: | --- | ||
| Target Release: | 4.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-04 10:47:31 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Seth Jennings
2019-04-12 18:12:35 UTC
Due to unstable map ordering https://github.com/openshift/cluster-kube-scheduler-operator/blob/master/pkg/operator/target_config_reconciler_v311_00.go#L151 PR soon. Bug went in on https://github.com/openshift/cluster-kube-scheduler-operator/pull/72 about 21 hours ago (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 Hi Seth, 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. https://access.redhat.com/errata/RHBA-2019:0758 |