Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1510292 - v3.7.0-0.196.0 ose image not pushed to reg-aws registry
Summary: v3.7.0-0.196.0 ose image not pushed to reg-aws registry
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Release
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.7.z
Assignee: Adam Haile
QA Contact: Chuan Yu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-07 06:42 UTC by Chuan Yu
Modified: 2018-10-08 13:17 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2018-10-08 13:17:38 UTC


Attachments (Terms of Use)

Description Chuan Yu 2017-11-07 06:42:45 UTC
Description of problem:
New build for OpenShift (Integration Testing): 3.7.0-0.196.0, the OSE image not pushed to registry.reg-aws.openshift.com:443

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

How reproducible:
always

Steps to Reproduce:
1.curl -H "Authorization: Bearer $(oc whoami -t)" https://registry.reg-aws.openshift.com/v2/openshift3/ose/tags/list | python -m json.tool 
2.
3.

Actual results:
No ose v3.7.0-0.196.0 image available

Expected results:
ose v3.7.0-0.196.0 image should be available in the registry

Additional info:

Comment 1 Justin Pierce 2017-11-07 19:14:07 UTC
There were errors during this build which should have terminated it. Instead it progressed to completion. Investigating.

Comment 2 Justin Pierce 2018-02-20 16:36:19 UTC
I believe root cause for this has been addressed. Please re-open if detected for new builds.

Comment 3 Chuan Yu 2018-02-23 05:21:13 UTC
Will re-open it when met this issue again.


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