Bug 1440309
| Summary: | [3.4] Post-install, master certs signed for wrong name | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Steven Walter <stwalter> | |
| Component: | Installer | Assignee: | Scott Dodson <sdodson> | |
| Status: | CLOSED ERRATA | QA Contact: | Gaoyun Pei <gpei> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 3.4.1 | CC: | aos-bugs, jialiu, jokerman, mmccomas, trogers | |
| Target Milestone: | --- | |||
| Target Release: | 3.4.z | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| 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: | ||||
| : | 1447398 1447399 (view as bug list) | Environment: | ||
| Last Closed: | 2017-05-17 17:39:21 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: | 1447398, 1447399 | |||
|
Description
Steven Walter
2017-04-07 21:05:05 UTC
Proposed fix here https://github.com/openshift/openshift-ansible/pull/3885 Example where ansible_host sorts differently from openshift_hostname, in this case oo_first_master will be master1 but openshift_ca will be master2 : [masters] master1 ansible_host=10.10.10.2 openshift_ip=10.10.10.2 openshift_public_ip=10.10.10.2 openshift_hostname=10.10.10.2 openshift_public_hostname=10.10.10.2 master2 ansible_host=10.10.10.1 openshift_ip=10.10.10.1 openshift_public_ip=10.10.10.1 openshift_hostname=10.10.10.1 openshift_public_hostname=10.10.10.1 master3 ansible_host=10.10.10.9 openshift_ip=10.10.10.9 openshift_public_ip=10.10.10.9 openshift_hostname=10.10.10.9 openshift_public_hostname=10.10.10.9 Verify this bug with openshift-ansible-3.4.82-1.git.0.c78ff1c.el7, after installation, all masters' certs were signed with correct ip address. 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/RHSA-2017:1244 |