Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1508724 - apb image from rhcc registry provision failed
apb image from rhcc registry provision failed
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker (Show other bugs)
3.7.0
Unspecified Unspecified
high Severity high
: ---
: 3.7.0
Assigned To: Ryan Hallisey
Zhang Cheng
: TestBlocker
: 1509246 (view as bug list)
Depends On:
Blocks: 1508278 1509018 1509271
  Show dependency treegraph
 
Reported: 2017-11-02 01:47 EDT by Zhang Cheng
Modified: 2017-11-28 17:20 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-11-28 17:20:57 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-28 21:34:54 EST

  None (edit)
Comment 1 Ryan Hallisey 2017-11-02 09:31:14 EDT
Can you attach the whole log from the broker and do an oc describe on the apb?
It seems like the docker image isn't found.  I'm wondering where the apb is looking.
Comment 3 Ryan Hallisey 2017-11-02 11:36:19 EDT
InspectFailed		Failed to apply default image tag "/openshift3/postgresql-apb:v3.7.0-0.189.0.0": couldn't parse image reference "/openshift3/postgresql-apb:v3.7.0-0.189.0.0": invalid reference format

"/openshift3/postgresql-apb:v3.7.0-0.189.0.0" This looks like you're missing the registry address. It should look like: "registry.access.stage.redhat.com/openshift3/postgresql-apb:v3.7.0-0.189.0.0"

Are you sure that you configured the registry correctly? I think there might be some flags you need: --add-registry=asb-registry.usersys.redhat.com:5000 --insecure-registry asb-registry.usersys.redhat.com:5000
Comment 6 Ryan Hallisey 2017-11-03 10:35:04 EDT
*** Bug 1509246 has been marked as a duplicate of this bug. ***
Comment 9 Ryan Hallisey 2017-11-06 09:38:13 EST
I don't see images with the tag v3.7.0-0.191.0.0. The latest I can find in the catalog is v3.7.0-0.189.0.0. Does it work with v3.7.0-0.189.0.0?
Comment 11 Ryan Hallisey 2017-11-06 10:40:22 EST
I didn't mean service-catalog and ansible-service-broker images. I meant the apb tags, sorry for not being specific. 

In the staged registry, the latest tags for apbs I can find is 'v3.7.0-0.189.0.0' and not 'v3.7.0-0.191.0.0'. My suggestion is to retest with the tag 'v3.7.0-0.189.0.0'.

https://access.stage.redhat.com/containers/?tab=tags#/registry.access.redhat.com/openshift3/postgresql-apb


    registry:
      - type: "rhcc"
        name: "rhcc"
        url: "registry.access.stage.redhat.com"
        tag:  v3.7.0-0.189.0.0
        white_list:
          - ".*-apb$"
Comment 12 Zhang Cheng 2017-11-06 10:46:00 EST
I will double confirm tomorrow. Thanks for your update.
Comment 17 errata-xmlrpc 2017-11-28 17:20:57 EST
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/RHSA-2017:3188

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