Bug 1624673 - No image automation-broker-apb in aws downstream registry
Summary: No image automation-broker-apb in aws downstream 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.z
Assignee: Jason Montleon
QA Contact: Zihan Tang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-03 03:09 UTC by Zihan Tang
Modified: 2019-01-10 09:04 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2019-01-10 09:03:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0024 0 None None None 2019-01-10 09:04:05 UTC

Description Zihan Tang 2018-09-03 03:09:58 UTC 
Description of problem:
automation-broker-apb:v3.11.0 is ready on brew registry,but has not been pushed to aws downstream registry,

curl -u *:* $AWS/v2/openshift3/automation-broker-apb/tags/list  | python -m json.tool 
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   140  100   140    0     0    117      0  0:00:01  0:00:01 --:--:--   117
{
    "errors": [
        {
            "code": "NAME_UNKNOWN",
            "detail": {
                "name": "openshift3/automation-broker-apb"
            },
            "message": "repository name not known to registry"
        }
    ]
}

please help push image to aws registry.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
automation-broker-apb:v3.11.0 is ready in aws registry.

Additional info:
Comment 5 Zihan Tang 2018-09-14 02:56:28 UTC 
Image not ready, move back to MODIFIED.
{
    "errors": [
        {
            "code": "NAME_UNKNOWN",
            "detail": {
                "name": "openshift3/automation-broker-apb"
            },
            "message": "repository name not known to registry"
        }
    ]
}
Comment 6 John Matthews 2018-09-19 14:03:46 UTC 
As per comment #3, the changes for this are on the RCM level of publishing images.

This BZ is not referring to any source code changes or features in the Broker.

Do we want to continue to track this as a BZ against 3.11.0?
Comment 7 Mark Lamourine 2018-09-19 14:07:53 UTC 
Adding this image is a current job.  It should not yet be marked as present.
Comment 8 Zihan Tang 2018-09-20 01:56:26 UTC 
This image is used for testing in aws/gce env , do not need any code changes as descriped in #comment6, so move it to 3.11.z to trace.
Comment 10 Zihan Tang 2018-09-27 05:58:52 UTC 
Image still not ready, move back to MODIFIED.
Comment 12 Zihan Tang 2018-09-28 08:39:09 UTC 
Image still not ready, move back to MODIFIED.
Comment 14 Zihan Tang 2018-10-09 02:53:13 UTC 
image in aws registry is ready, change it to ON_QA
Comment 15 Zihan Tang 2018-10-09 02:54:49 UTC 
 automation-broker-apb image is ready , change it VERIFIED.
{
    "name": "openshift3/automation-broker-apb",
    "tags": [
        "v3.11.19",
        "v3.11.21",
        "v3.11.21-1",
        "v3.11",
        "v3.11.18",
        "v3.11.18-1",
        "v3.11.19-1",
        "v3.11.20",
        "v3.11.20-1"
    ]
}
Comment 17 errata-xmlrpc 2019-01-10 09:03:58 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-2019:0024
Note You need to log in before you can comment on or make changes to this bug.