Bug 1746499 - Attempts to push build output to external registry fail
Summary: Attempts to push build output to external registry fail
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2.0
Assignee: Nalin Dahyabhai
QA Contact: wewang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-28 15:27 UTC by rvanderp
Modified: 2019-10-29 21:47 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: due to a logic bug, attempts to push an image to a registry after it was built would fail if the build's BuildConfig specified an output of type DockerImage, but the name which was specified for that output image did not include a tag component. Consequence: The attempt to push a built image would fail. Fix: The builder now adds the "latest" tag to a name if one is not specified. Result: An image built using a BuildConfig which specifies an output of type DockerImage, with a name that does not include a tag component, will now be pushed using the "latest" tag.
Clone Of:
Environment:
Last Closed: 2019-10-16 06:38:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift builder pull 92 0 'None' closed Bug 1746499: Add ":latest" to push tag if none is specified 2020-10-06 01:02:19 UTC
Github openshift origin pull 23698 0 'None' closed Bug 1746499: Ensure images push without full tag spec 2020-10-06 01:02:27 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:40:23 UTC

Comment 10 Miheer Salunke 2019-08-29 07:46:32 UTC 
Shall we collect ?

1) Quay registry logs 

2) tcp dump for push fail
Comment 23 errata-xmlrpc 2019-10-16 06:38:14 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:2922
Note You need to log in before you can comment on or make changes to this bug.