Bug 1442009 - [3.4]Failed to redeploy CA certificates on Atomic Hosts
Summary: [3.4]Failed to redeploy CA certificates on Atomic Hosts
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.4.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.4.z
Assignee: Tim Bielawa
QA Contact: Gaoyun Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-13 10:02 UTC by Gaoyun Pei
Modified: 2017-07-27 18:02 UTC (History)
6 users (show)

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.
Clone Of: 1427067
Environment:
Last Closed: 2017-07-27 18:02:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1810 0 normal SHIPPED_LIVE OpenShift Container Platform atomic-openshift-utils bug fix and enhancement 2017-07-27 21:58:37 UTC

Comment 1 Scott Dodson 2017-06-12 14:13:59 UTC
https://github.com/openshift/openshift-ansible/pull/3633 need to backport?

Comment 4 Gaoyun Pei 2017-07-10 06:03:24 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.

Comment 6 errata-xmlrpc 2017-07-27 18:02:01 UTC
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


Note You need to log in before you can comment on or make changes to this bug.