Bug 1442009
| Summary: | [3.4]Failed to redeploy CA certificates on Atomic Hosts | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Gaoyun Pei <gpei> |
| Component: | Installer | Assignee: | Tim Bielawa <tbielawa> |
| Status: | CLOSED ERRATA | QA Contact: | Gaoyun Pei <gpei> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.4.1 | CC: | aos-bugs, ghuang, gpei, jokerman, mmccomas, tbielawa |
| Target Milestone: | --- | ||
| Target Release: | 3.4.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: The fact "etcd_is_atomic" was detected incorrectly due to the role ordering of some fact setting operations. Atomic Hosts do not support yum/repoquery/rpm commands.
Consequence: Atomic Hosts would attempt to run commands specific to managing/inspecting repositories and packages when they should not.
Fix: The ordering of role calls and fact updates was changed and wrapped in a meta-role to ensure they stay in the correct order.
Result: Atomic Hosts will not attempt to run unsupported rpm/yum/repoquery type commands because the etcd_is_atomic fact is correctly detected.
|
Story Points: | --- |
| Clone Of: | 1427067 | Environment: | |
| Last Closed: | 2017-07-27 18:02:01 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: | |||
|
Comment 1
Scott Dodson
2017-06-12 14:13:59 UTC
Verify this bug with openshift-ansible-3.4.113-1.git.0.3bc2eff.el7.noarch.rpm. Redeploy openshift ca and etcd ca playbook could run well against 3.4 env on Atomic Host. 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-2017:1810 |