Bug 1576881

Summary: [RFE] Add PartnerRhcc Registry Adapter
Product: OpenShift Container Platform Reporter: Dylan Murray <dymurray>
Component: Service BrokerAssignee: Dylan Murray <dymurray>
Status: CLOSED ERRATA QA Contact: Zhang Cheng <chezhang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.9.0CC: aos-bugs, chezhang, jiazha, zhsun, zitang
Target Milestone: ---   
Target Release: 3.10.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Enhancement
Doc Text:
Add type: partner_rhcc registry adapter which works with https://regsitry.connect.redhat.com
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-30 19:14: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:

Description Dylan Murray 2018-05-10 15:35:02 UTC
Description of problem:
In 3.9 if a user wanted to use `type: openshift` registry adapter, they must also include a list of images that they want to bootstrap. This is because there was no implementation of the catalog API which allows us to discover APB images. We should attempt to grab a list of images off /v2/_catalog if `images` is not populated in the config.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Remove `images` from registry config
2. Set URL to https://registry.connect.redhat.com

Actual results:
Bootstrap fails to find any images

Expected results:
Bootstrap finds rocketchat/rocketchat-apb

Additional info:

Comment 2 Dylan Murray 2018-05-16 12:13:19 UTC
Due to some confusion around the different registries... we have instead added a new registry adapter which is type: partner_rhcc which works with https://registry.connect.redhat.com.

This is because `openshift` registry still doesn't support discovery but https://registry.connect.redhat.com using a proxy does support discovery. To avoid confusion we will keep these as different adapters.

Comment 5 David Zager 2018-05-24 20:18:24 UTC
Once https://github.com/openshift/ansible-service-broker/pull/968 is merged, the next release of the broker will have this fix.

Comment 9 errata-xmlrpc 2018-07-30 19:14: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.