Bug 1622966
| Summary: | Cannot load apb specs while using partner_rhcc registry | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Zhang Cheng <chezhang> |
| Component: | Service Broker | Assignee: | Dylan Murray <dymurray> |
| Status: | CLOSED ERRATA | QA Contact: | Zhang Cheng <chezhang> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.11.0 | CC: | aos-bugs, jiazha, jmatthew, zitang |
| Target Milestone: | --- | ||
| Target Release: | 3.11.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-10-11 07:25:54 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: | |||
|
Comment 1
Dylan Murray
2018-08-30 18:48:41 UTC
Advisory has been updated with the following new builds: openshift-enterprise-mariadb-apb-v3.11.0-0.25.0.1 openshift-enterprise-postgresql-apb-v3.11.0-0.25.0.1 openshift-enterprise-mysql-apb-v3.11.0-0.25.0.1 openshift-enterprise-apb-tools-container-v3.11.0-0.26.0.0 openshift-enterprise-asb-container-v3.11.0-0.26.0.0 automation-broker-apb-v3.11.0-0.20.0.5 Advisory has been updated with the following builds: openshift-enterprise-apb-base-container-v3.11.0-0.11.0.2 openshift-enterprise-mediawiki-apb-v3.11.0-0.0.4242.lmeyer.2 openshift-enterprise-mariadb-apb-v3.11.0-0.25.0.3 openshift-enterprise-postgresql-apb-v3.11.0-0.25.0.4 openshift-enterprise-mysql-apb-v3.11.0-0.25.0.3 openshift-enterprise-apb-tools-container-v3.11.0-0.26.0.1 openshift-enterprise-asb-container-v3.11.0-0.26.0.1 automation-broker-apb-v3.11.0-0.20.0.6 Test Passed and Changing status to VERIFIED. Test asb version: 1.3.15 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:2652 |