Bug 1649063
Summary: | Binary builds are not automatically including the pull secret from the service account during the build. | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Ben Parees <bparees> |
Component: | Build | Assignee: | Ben Parees <bparees> |
Status: | CLOSED ERRATA | QA Contact: | wewang <wewang> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.0 | CC: | aos-bugs, florin.peter, jkaur, wewang, wzheng |
Target Milestone: | --- | ||
Target Release: | 4.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
Feature: Builds that do not explicitly indicate the docker image they consume (by providing an inline dockerfile or defining the docker strategy's From field) and do not explicitly indicate a pull secret to use, will now use the build's service account's docker secret by default. Examples of such builds would be a build that includes a Dockerfile in a git repo.
Reason: Previously these builds would use no secret and potentially fail if the base image was not public.
Result: Those builds will now succeed without the need to either explicitly specify a pull secret, or explicitly specify the base image in the buildconfig.
|
Story Points: | --- |
Clone Of: | 1648775 | Environment: | |
Last Closed: | 2019-06-04 10:40:51 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: | |||
Bug Depends On: | 1648775 | ||
Bug Blocks: | 1649062 |
Description
Ben Parees
2018-11-12 20:05:47 UTC
this has been in modified for 2 weeks. whatever script is supposed to be moving things to on_qa is not working. Verified in openshift: v4.0.0-0.80.0 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:0758 |