Catalog discovery with Ansible Service Broker not working when using apiv2 type registry in OpenShift Container Platform
Issue
- We deployed Ansible Service Broker (ASB) on OpenShift 3.11 with registry
type: apiv2
. When starting the Ansible Service Broker pod, it fails with the following error:
time="2019-05-28T13:56:58Z" level=debug msg="fooregistry - discoverImages"
time="2019-05-28T13:57:09Z" level=debug msg="Properly unmarshalled image response"
time="2019-05-28T13:57:09Z" level=debug msg="discovered images from - https://registry.foo.example.com/v2/_catalog "
time="2019-05-28T13:57:10Z" level=warning msg="Failed to fetch catalog response from 'https://registry.foo.example.com/v2/_catalog?last=bar/abc&n=0'. Expected a 200 status and got: 404 Not Found"
time="2019-05-28T13:57:10Z" level=error msg="unable to retrieve image names for registry fooregistry - failed to fetch catalog response: [404 Not Found] and failed to find images in configuration"
time="2019-05-28T13:57:10Z" level=warning msg="registry: 0x15665f0 was unable to complete bootstrap - failed to fetch catalog response: [404 Not Found] and failed to find images in configuration"
time="2019-05-28T13:57:10Z" level=error msg="Failed to bootstrap on startup!"
time="2019-05-28T13:57:10Z" level=error msg="all registries failed on bootstrap"
Environment
- Red Hat OpenShift Container Platform 3.11
- Ansible Service Broker
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.