Bug 1447398

Summary: [3.3] Post-install, master certs signed for wrong name
Product: OpenShift Container Platform Reporter: Scott Dodson <sdodson>
Component: InstallerAssignee: Scott Dodson <sdodson>
Status: CLOSED ERRATA QA Contact: Gaoyun Pei <gpei>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.3.1CC: aos-bugs, jialiu, jokerman, mmccomas, stwalter, trogers
Target Milestone: ---   
Target Release: 3.3.1   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
In multi-master environments if ansible_host and openshift_hostname values differ and ansible sorts one of the lists differently from the other then the CA Host may be the first master but it was still signing the initial certificates with the hostnames of the first master. By ensuring that we use the hostnames of the CA Host when creating the certificate authority we ensure that the certificates are signed with the correct hostnames even if the two lists are sorted differently.
Story Points: ---
Clone Of: 1440309 Environment:
Last Closed: 2017-05-17 17:40:44 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:
Bug Depends On: 1440309, 1447399    
Bug Blocks:    

Comment 3 Gaoyun Pei 2017-05-08 10:28:54 UTC
Verify this bug with openshift-ansible-3.3.75-1.git.0.ce1661a.el7.noarch.rpm, after installation, all masters' certs were signed with correct ip address, the cluster was working well.

Comment 5 errata-xmlrpc 2017-05-17 17:40:44 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.