Description of problem: After installation, scheduler does not use schedulerConfigfile and create from the defaultprovider, and we have to use the following lines to make the schedulerConfigFile back to work on kubenetes 1.9: kubernetesMasterConfig: ...... schedulerArguments: use-legacy-policy-config: - "true" schedulerConfigFile: /etc/origin/master/scheduler.json Version-Release number of the following components: openshift-ansible-3.9.0-0.34.0.git.0.c7d9585.el7.noarch.rpm ansible-2.4.2.0-2.el7.noarch.rpm # openshift version openshift v3.9.0-0.34.0 kubernetes v1.9.1+a0ce1bc657 etcd 3.2.8 How reproducible: Steps to Reproduce: 1. After installation checked logs for service atomic-openshift-master-controllers 2. 3. Actual results: scheduler start with defaultprovider Expected results: scheduler should start from the given config file Additional info: for 3.8, schedulerConfigFile still work.
Due to this PR https://github.com/openshift/origin/pull/18139 came in.
Ravi, could you take a look?
Origin PR: https://github.com/openshift/origin/pull/18475 Moving it to Post now.
Checked with # openshift version openshift v3.9.2 kubernetes v1.9.1+a0ce1bc657 etcd 3.2.16 And the issue can not be reproduced, so verify this.
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-2018:0489