Bug 1736795
| Summary: | Remove scheduler-policy then recover name to original "" in scheduler/cluster still result in scheduler pod CrashLoopBackOff | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | ge liu <geliu> |
| Component: | kube-scheduler | Assignee: | Mike Dame <mdame> |
| Status: | CLOSED ERRATA | QA Contact: | Xingxing Xia <xxia> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.2.0 | CC: | aos-bugs, mdame, mfojtik, xxia |
| Target Milestone: | --- | ||
| Target Release: | 4.2.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-16 06:34:29 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: | |
| Embargoed: | |||
I've started diagnosing this in https://github.com/openshift/cluster-kube-scheduler-operator/pull/164 There are a couple issues here, as I described in my pr but: 1. Kube-scheduler-operator doesn't act on an empty Spec.Policy.Name field, it only checks for it then throws it away if it is empty. 2. The generic operator client in library-go currently has a bug that doesn't account for removing fields from observed config. This is a big cause of our problem but, due to issue 1, not an exact duplicate. We can fix 1, but it won't have any effect until 2 is resolved, so until then we depend on that bug Now that https://bugzilla.redhat.com/show_bug.cgi?id=1738432 has been verified this should also be verified Verified in 4.2.0-0.nightly-2019-08-22-043819 , scheduler/cluster can change the name to "" and the pods can terminate and be re-running 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:2922 |
oc edit kubescheduler cluster spec: logLevel: "" managementState: Managed observedConfig: algorithmSource: policy: configMap: name: policy-configmap namespace: openshift-kube-scheduler Remove observedConfig, save and exit, scheduler pod will recover to Running. But from above description, user customizes policy via `oc edit scheduler cluster`, so should user un-customize policy via `oc edit scheduler cluster` to name: ""