Bug 1746499
| Summary: | Attempts to push build output to external registry fail | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | rvanderp |
| Component: | Build | Assignee: | Nalin Dahyabhai <nalin> |
| Status: | CLOSED ERRATA | QA Contact: | wewang <wewang> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.1.0 | CC: | adam.kaplan, aos-bugs, maupadhy, misalunk, nalin, rhowe, wzheng |
| Target Milestone: | --- | ||
| Target Release: | 4.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-16 06:38:14 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 10
Miheer Salunke
2019-08-29 07:46:32 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 |