Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1540785

Summary: From OpenShift 3.9 schedulerConfigFile have to work with use-legacy-policy-config
Product: OpenShift Container Platform Reporter: weiwei jiang <wjiang>
Component: NodeAssignee: ravig <rgudimet>
Status: CLOSED ERRATA QA Contact: DeShuai Ma <dma>
Severity: medium Docs Contact:
Priority: high    
Version: 3.9.0CC: aos-bugs, avagarwa, jokerman, mmccomas, sjenning, wmeng
Target Milestone: ---   
Target Release: 3.9.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: 2018-03-28 14:24:57 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:

Description weiwei jiang 2018-02-01 02:10:30 UTC
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.

Comment 1 weiwei jiang 2018-02-01 02:11:58 UTC
Due to this PR https://github.com/openshift/origin/pull/18139 came in.

Comment 2 Seth Jennings 2018-02-01 23:05:30 UTC
Ravi, could you take a look?

Comment 4 Avesh Agarwal 2018-02-06 17:04:02 UTC
Origin PR:
https://github.com/openshift/origin/pull/18475

Moving it to Post now.

Comment 6 weiwei jiang 2018-03-05 02:59:52 UTC
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.

Comment 9 errata-xmlrpc 2018-03-28 14:24:57 UTC
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