Bug 1622966 - Cannot load apb specs while using partner_rhcc registry
Summary: Cannot load apb specs while using partner_rhcc registry
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.11.0
Assignee: Dylan Murray
QA Contact: Zhang Cheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-28 09:27 UTC by Zhang Cheng
Modified: 2018-10-11 07:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-11 07:25:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 0 None None None 2018-10-11 07:26:26 UTC

Comment 2 Dylan Murray 2018-08-31 18:21:52 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

Comment 4 Dylan Murray 2018-09-04 15:54:23 UTC
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

Comment 5 Zhang Cheng 2018-09-05 09:26:02 UTC
Test Passed and Changing status to VERIFIED.

Test asb version: 1.3.15

Comment 7 errata-xmlrpc 2018-10-11 07:25:54 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-2018:2652


Note You need to log in before you can comment on or make changes to this bug.