Bug 1832975
Summary: | Panic in openshift/builder imagebuilder processing dockerfile ARG step | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> |
Component: | Build | Assignee: | Gabe Montero <gmontero> |
Status: | CLOSED ERRATA | QA Contact: | wewang <wewang> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.4 | CC: | adam.kaplan, ansverma, aos-bugs, maupadhy, wzheng |
Target Milestone: | --- | ||
Target Release: | 4.3.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: Dockerfile parsing in openshift/builder was not initializing a map need for processing any ARG steps
Consequence: OpenShift Docker Strategy Builds where the Dockerfile had an ARG step would panic and fail prior to invoking buildah.
Fix: Initialized the map related to ARG step processing so golang would not panic on a nil reference.
Result: OpenShift Docker Strategy Builds where the Dockerfile has an ARG step will not panic prior to invoking buildah.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-05-27 17:00:46 UTC | Type: | --- |
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: | 1801388 | ||
Bug Blocks: |
Description
OpenShift BugZilla Robot
2020-05-07 14:48:02 UTC
Verified in version: 4.3.0-0.nightly-2020-05-14-202241 Steps: 1. Use bc to create build apiVersion: build.openshift.io/v1 kind: BuildConfig metadata: name: sample-build-docker-args-preset spec: source: dockerfile: |- ARG foo=ab FROM centos type: Dockerfile strategy: dockerStrategy: {} type: Docker 2. Check the build [wewang@wangwen ~]$ oc get builds NAME TYPE FROM STATUS STARTED DURATION sample-build-docker-args-preset-1 Docker Dockerfile Complete 45 seconds ago 35s 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-2020:2184 |