Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1433068

Summary: [3.3] Certificate redeploy playbook shouldn't remove CA certificate by default
Product: OpenShift Container Platform Reporter: Andrew Butcher <abutcher>
Component: InstallerAssignee: Andrew Butcher <abutcher>
Status: CLOSED ERRATA QA Contact: Gaoyun Pei <gpei>
Severity: high Docs Contact:
Priority: high    
Version: 3.3.1CC: aos-bugs, bleanhar, dlbewley, gpei, jialiu, jokerman, mmccomas, sdodson, stwalter, tkimura
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1427429 Environment:
Last Closed: 2017-04-25 17:42:31 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: 1427429    
Bug Blocks:    

Comment 3 Gaoyun Pei 2017-04-13 08:07:29 UTC
Verify this bug with openshift-ansible-3.3.72-1.git.0.d10f480.el7.noarch.

Redeploy certificates(master, etcd, node, registry, and router certificates) using the current CA certificate.
 
ansible-playbook -i host /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/redeploy-certificates.yml

After certificates redeployment, CA certificates were not updated, ocp-3.3 cluster was working well.


And the CA certificates could be replaced by running the specialized redeploy-openshift-ca.yml playbook, it could redeploy the CA certificates(including etcd CA) by generating new CA certificate and distributing an updated bundle to all necessary components.

ansible-playbook -i host /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/redeploy-openshift-ca.yml

After CA certificates updated, ocp-3.3 cluster was still working well.

Comment 5 errata-xmlrpc 2017-04-25 17:42:31 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:1140