Discussed with developers in the email, the related PR is here: https://github.com/automationbroker/bundle-lib/pull/109

https://github.com/automationbroker/bundle-lib/pull/132

https://errata.devel.redhat.com/advisory/33505 updated

openshift-enterprise-mariadb-apb-v3.11.0-0.10.0.3
openshift-enterprise-mediawiki-apb-v3.11.0-0.10.0.3
openshift-enterprise-postgresql-apb-v3.11.0-0.10.0.3
openshift-enterprise-mysql-apb-v3.11.0-0.10.0.3
openshift-enterprise-mediawiki-container-v3.11.0-0.10.0.0
openshift-enterprise-asb-container-v3.11.0-0.10.0.1
openshift-enterprise-apb-base-container-v3.11.0-0.10.0.3

Moving back to POST so that David can rebuild once this code is in the broker repo.

https://github.com/openshift/ansible-service-broker/pull/1040

Upstream doc update.

https://github.com/automationbroker/bundle-lib/pull/163

As you can see in your logs the error message is just warning the user that there is no /v2/_catalog endpoint on this registry. The broker is successfully bootstrapping the images even though you saw this error.

I have changed it from an error to a warning and added explicit error messages.

Verified with 1.3.9

Have changed to "warning":

time="2018-08-16T06:23:32Z" level=warning msg="Failed to fetch catalog response from 'http://brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/v2/_catalog'. Expected a 200 status and got: 404 NOT FOUND"

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