Bug 1523625
Summary: | service catalog deployment fails | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jaspreet Kaur <jkaur> |
Component: | Service Broker | Assignee: | Jeff Peeler <jpeeler> |
Status: | CLOSED ERRATA | QA Contact: | Jian Zhang <jiazha> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 3.7.0 | CC: | abutcher, aivaras.laimikis, aos-bugs, bmchugh, chezhang, chrkim, dcaldwel, dmoessne, erjones, fshaikh, ggore, jiazha, jkaur, jmalde, jokerman, jpeeler, jrosenta, mmccomas, mrobson, nbhatt, nnosenzo, pmorie, rbost, rhowe, sgaikwad, smunilla, snalawad, tibrahim, vwalek, wdecoste, wmeng |
Target Milestone: | --- | ||
Target Release: | 3.7.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openshift-ansible-3.7.24-1.git.0.18a2c6a.el7 | Doc Type: | Bug Fix |
Doc Text: |
The ansible installer previously was not updating the api service definition with newly generated certificate data. Also, the service catalog api server wasn't being restarted to pick up the new certs either. Using mismatched CAs causes x509 errors in the api server logs and has now been corrected.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-05 09:33:10 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: |
Description
Jaspreet Kaur
2017-12-08 12:23:43 UTC
*** Bug 1526150 has been marked as a duplicate of this bug. *** The workaround for this bug is to update the service catalog apiservice. Set the ca_bundle field to the base64 encoded contents of /etc/origin/service-catalog/ca.crt and then delete the apiservice pod. When it's recreated it should work. cat /etc/origin/service-catalog/ca.crt | base64 oc edit apiservice/v1beta1.servicecatalog.k8s.io update ca_bundle field with the base64 encoded content from the first command *** Bug 1539634 has been marked as a duplicate of this bug. *** 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-2018:0636 |