Bug 1652191
Summary: | [3.10] Setting openshift_use_crio=false per group is ignored and node-config is modified | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Russell Teague <rteague> | |
Component: | Installer | Assignee: | Russell Teague <rteague> | |
Installer sub component: | openshift-ansible | QA Contact: | Weihua Meng <wmeng> | |
Status: | CLOSED ERRATA | Docs Contact: | ||
Severity: | unspecified | |||
Priority: | unspecified | CC: | aos-bugs, eminguez, gpei, jialiu, jokerman, mmccomas, wmeng | |
Version: | 3.10.0 | Keywords: | Triaged | |
Target Milestone: | --- | |||
Target Release: | 3.10.z | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Cause: Node configmaps are all created by running create tasks on the first master.
Consequence: If the first master has openshift_use_crio=True, all configmaps are created with crio settings because the node-config template has crio settings as part of the template based on that host var.
Fix: The crio settings have been removed from the node-config template so that crio settings will only be added fi they are part of the openshift_node_group edits. Additionally, the bootstrap-node-config is updated directly if the host openshift_use_crio=True.
Result: Node configmaps are generated correctly based on openshift_node_group edits allowing nodes to be properly configured with crio settings.
|
Story Points: | --- | |
Clone Of: | 1647516 | |||
: | 1656359 (view as bug list) | Environment: | ||
Last Closed: | 2018-12-13 17:09:08 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: | 1647516 | |||
Bug Blocks: |
Description
Russell Teague
2018-11-21 16:23:40 UTC
Fixed. openshift-ansible-3.10.83-1.git.0.12699eb.el7.noarch node-config are correct for crio container-runtime nodes and docker container-runtime nodes. Kernel Version: 3.10.0-957.1.3.el7.x86_64 Operating System: Red Hat Enterprise Linux Server 7.6 (Maipo) 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:3750 |