Bug 1309435
| Summary: | namedCertificates do not match the wild card certificate | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Kenny Woodson <kwoodson> |
| Component: | apiserver-auth | Assignee: | Jordan Liggitt <jliggitt> |
| Status: | CLOSED ERRATA | QA Contact: | weiwei jiang <wjiang> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.1.0 | CC: | agrimm, aos-bugs, tdawson, wjiang, wsun |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | atomic-openshift-3.1.1.905-1.git.0.ef5902f.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-12 16:29: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: | 130 | ||
Hostname verification merged upstream in https://github.com/openshift/origin/pull/7399 Checked with devenv-rhel7_3509 and openshift v3.1.1.905 kubernetes v1.2.0-alpha.7-703-gbc4550d etcd 2.2.5 The bug can not be reproduced. 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-2016:1064 |
Description of problem: When installing and configuring a cluster recently we added our SSL certificate to the master-config file and we added our configuration to the namedCertificates. master-config.yml: namedCertificates: - certFile: /etc/origin/master/named_certificates/star_tsi_openshift_com.crt keyFile: /etc/origin/master/named_certificates/tsi.key names: - "api.tsi.openshift.com" - "console.tsi.openshift.com" We then proceeded to see this error: Feb 17 13:17:07 ip-172-31-48-111.ec2.internal atomic-openshift-master-controllers[33594]: W0217 13:17:07.639989 33594 start_master.go:269] servingInfo.namedCertificates[0].names[0]: invalid value 'api.tsi.openshift.com', Details: the specified certificate does not have a CommonName or DNS subjectAltName that matches this name Feb 17 13:17:07 ip-172-31-48-111.ec2.internal atomic-openshift-master-controllers[33594]: W0217 13:17:07.640112 33594 start_master.go:269] servingInfo.namedCertificates[0].names[1]: invalid value 'config.tsi.openshift.com', Details: the specified certificate does not have a CommonName or DNS subjectAltName that matches this name The certificate is a wild card certificate: Subject: C=US, ST=North Carolina, L=Raleigh, O=Red Hat Inc.,CN=*.tsi.openshift.com SLL command: openssl x509 -in /etc/origin/master/named_certificates/star_tsi_openshift_com.crt -text -noout | grep -A 1 "Subject Alternative Name" X509v3 Subject Alternative Name: DNS:*.tsi.openshift.com, DNS:tsi.openshift.com Version-Release number of selected component (if applicable): 3.1.1.6-2 How reproducible: I'm not sure but we saw this on a fresh create and using the openshift-ansible byo playbooks. Steps to Reproduce: 1. Set the values in /etc/origin/master-config.yml correctly. (those mentioned above) 2. Attempt to start the master service. systemctl restart atomic-openshift-master-controllers.service 3. Look for the error message in the journal. journalctl -lu atomic-openshift-master-controllers Actual results: We are seeing that the wild card does not match the names given. Expected results: The names should match and we should not see the error. Additional info: