Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1540785 - From OpenShift 3.9 schedulerConfigFile have to work with use-legacy-policy-config
From OpenShift 3.9 schedulerConfigFile have to work with use-legacy-policy-co...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Pod (Show other bugs)
3.9.0
Unspecified Unspecified
high Severity medium
: ---
: 3.9.0
Assigned To: ravig
DeShuai Ma
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-01-31 21:10 EST by weiwei jiang
Modified: 2018-03-28 10:25 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-03-28 10:24:57 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 None None None 2018-03-28 10:25 EDT

  None (edit)
Description weiwei jiang 2018-01-31 21:10:30 EST
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-01-31 21:11:58 EST
Due to this PR https://github.com/openshift/origin/pull/18139 came in.
Comment 2 Seth Jennings 2018-02-01 18:05:30 EST
Ravi, could you take a look?
Comment 4 Avesh Agarwal 2018-02-06 12:04:02 EST
Origin PR:
https://github.com/openshift/origin/pull/18475

Moving it to Post now.
Comment 6 weiwei jiang 2018-03-04 21:59:52 EST
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 10:24:57 EDT
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

Note You need to log in before you can comment on or make changes to this bug.