Bug 1634700
Summary: | [3.11] Modification in master-config.yaml is causing a failure during Master-API restart (runtime-config) | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Simon Reber <sreber> | |
Component: | Installer | Assignee: | Scott Dodson <sdodson> | |
Status: | CLOSED ERRATA | QA Contact: | ge liu <geliu> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 3.10.0 | CC: | aos-bugs, cshereme, geliu, gpei, jokerman, mmccomas, rhowe, sdodson | |
Target Milestone: | --- | |||
Target Release: | 3.11.z | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Previously, when upgrading from earlier versions of the product the step that removes pod presets configuration may have resulted in a master-config.yaml file that failed to parse properly. This error has been corrected and the master-config.yaml should now be updated properly in all scenarios.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1642148 (view as bug list) | Environment: | ||
Last Closed: | 2018-11-20 03:10:46 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1642148 |
Description
Simon Reber
2018-10-01 11:37:27 UTC
*** Bug 1633383 has been marked as a duplicate of this bug. *** https://github.com/openshift/openshift-ansible/pull/10495 release-3.11 backport Upgrade from 3.10 to 3.11 successfully, In 3.10 env, master-config.yaml have not runtime-config items already, and after upgrade to 3.11(v3.11.36), there is not runtime-config exist yet. version: atomic-openshift-3.11.36-1.git.0.9c078f1.el7.x86_64 There is still problem in upgrade.yml, : ######################################################################## - name: Find current value for runtime-config yedit: src: "/tmp/master-config.yaml" ====>It should be '{{ openshift.common.config_base }}/master/' key: "kubernetesMasterConfig.apiServerArguments.runtime-config" state: list register: runtime_config - name: Set the runtime-config to exclude pod presets #################################################################### "/tmp/master-config.yaml" is not wrong directory, so it will not list the runtime_config, then the next steps will be skill by playbook, so this error need to be executed. Nice catch, thanks. https://github.com/openshift/openshift-ansible/pull/10583 In openshift-ansible-3.11.39-1 and later Verified. openshift-ansible-3.11.41-1.git.0.f711b2d.el7.noarch after upgrade 3.9-->3.10-->3.11, the runtime_config item exists in master-config.yaml, and the value is:[], It's work as design according to ansible playbook, but I have a question: if upgrade from fresh install 3.10->3.11, there is not runtime_config item in master_config.yaml, but upgrade env will have it, so is this difference make any effect for ocp? thx The main thing we're interested in fixing is that no matter the starting state the api server is able to parse the configuration file and run successfully. I think what you're describing indicates there's no problem, right? Upgrade is works well, Wish there is not potential risk from the difference of fresh installed and upgraded env about the runtime_config item. 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:3537 |