Bug 1810491
| Summary: | openshift-installer does only import a singe CA from clouds.yaml "cacert" bundle for OpenShift on OpenStack | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Martin André <m.andre> |
| Component: | Installer | Assignee: | Martin André <m.andre> |
| Installer sub component: | OpenShift on OpenStack | QA Contact: | David Sanz <dsanzmor> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | high | CC: | asimonel, dsanzmor, m.andre, pprinett, rheinzma |
| Version: | 4.3.z | ||
| Target Milestone: | --- | ||
| Target Release: | 4.4.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: When the CA cert file referenced from the clouds.yaml contained more than one certificate, the complete cert bundle was added to the bootstrap ignition file, but only the first one was actually trusted to gather the ignition file.
Consequence: It was not possible to install OCP on OpenStack environment using intermediate certificates signed by non-default trusted authority.
Fix: Split the CA cert bundle into separate certs and add them to the ignition file as separate entries.
Result: It is now possible to install OCP on OpenStack environment using intermediate certificates signed by non-default trusted authorities.
|
Story Points: | --- |
| Clone Of: | 1809780 | Environment: | |
| Last Closed: | 2020-05-13 22:00:53 UTC | Type: | --- |
| 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: | 1809780 | ||
| Bug Blocks: | 1810492 | ||
|
Comment 3
David Sanz
2020-03-30 13:26:22 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-2020:0581 |