Bug 1611247
Summary: | update scheduler.json of master can not take effect | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | MinLi <minmli> |
Component: | Node | Assignee: | Seth Jennings <sjenning> |
Status: | CLOSED ERRATA | QA Contact: | Xiaoli Tian <xtian> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.11.0 | CC: | aos-bugs, jokerman, minmli, mmccomas, sjenning |
Target Milestone: | --- | ||
Target Release: | 4.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-04 10:40:22 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
MinLi
2018-08-02 08:15:52 UTC
this problem happen definitely in aws env, template: http://git.app.eng.bos.redhat.com/git/openshift-misc.git/plain/v3-launch-templates/functionality-testing/aos-3_11/vars-aws/rpm-rhel7-s3_registry-aws-cloudprovider But in other env, such as gce , it not happen I am not able to reproduce this, as everything is working as expected. I did following steps and it is evident from the logs, the scheduler was started with updated scheduler.json: 1.Updated debug level in /etc/origin/master/master.env: DEBUG_LOGLEVEL=10 2. Used following scheduler.json: scheduler.json as follows: { "apiVersion": "v1", "kind": "Policy", "predicates": [ { "name": "GeneralPredicates" } ], "priorities": [ { "name": "BalancedResourceAllocation", "weight": 4 } ] } 3. Restarted controllers on master: #/usr/local/bin/master-restart controllers 4. Here are the logs: I0806 20:07:21.733455 1 factory.go:960] Creating scheduler from configuration: {{ } [{GeneralPredicates <nil>}] [{BalancedResourceAllocation 4 <nil>}] [] 0 false} I0806 20:07:21.733522 1 factory.go:977] Registering predicate: GeneralPredicates I0806 20:07:21.733556 1 plugins.go:224] Predicate type GeneralPredicates already registered, reusing. I0806 20:07:21.733584 1 factory.go:992] Registering priority: BalancedResourceAllocation I0806 20:07:21.733632 1 plugins.go:336] Priority type BalancedResourceAllocation already registered, reusing. I0806 20:07:21.733670 1 factory.go:1049] Creating scheduler with fit predicates 'map[GeneralPredicates:{}]' and priority functions 'map[BalancedResourceAllocation:{}]' I have my 3.11 cluster running in AWS in case you want to verify. I test again in aws cluster When do step4 "master-restart controllers" it print "2". I think this cause scheduler.json not effect. Because I run the command in gce cluster, it not print anything. I want to know if you meet the same problem. can i get access to your aws cluster? It seems this issue not happen any more. As comment 9, move to verified. verified version: oc v3.11.57 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://ip-172-18-15-99.ec2.internal:8443 openshift v3.11.57 kubernetes v1.11.0+d4cacc0 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 |