Bug 1724718
Summary: | 3.11.123 prerequisites playbook fails because openshift_use_crio is not defined | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Candace Sheremeta <cshereme> |
Component: | Installer | Assignee: | Russell Teague <rteague> |
Installer sub component: | openshift-ansible | QA Contact: | Weihua Meng <wmeng> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | unspecified | CC: | jialiu, wmeng |
Version: | 3.11.0 | ||
Target Milestone: | --- | ||
Target Release: | 3.11.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: In some cases, defaults were not loaded for hosts during sanity checks.
Consequence: Sanity checks would fail.
Fix: Added a step to run openshift_facts to load all defaults.
Result: Defaults are loaded for all hosts and sanity checks run successfully.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-07-23 19:56:39 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: | 1710020 |
Description
Candace Sheremeta
2019-06-27 15:44:47 UTC
I was not able to reproduce this issue however a PR has been opened to ensure all defaults are loaded for all hosts during sanity checks. https://github.com/openshift/openshift-ansible/pull/11724 I can reproduce this. Fixed in openshift-ansible-3.11.124 Hi, Candace Although this bug is fixed, install is likely to fail due to not meet selinux settings this is from master sosreport SELINUX=permissive https://docs.openshift.com/container-platform/3.11/install/prerequisites.html#prereq-selinux Hey Weihua, Excellent catch, thank you so much! Verified. 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:1753 |