Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1598013

Summary: [Trello_wpQi7K7r] s2i build with "--as-dockerfile=Dockerfile" should give path error info
Product: OpenShift Container Platform Reporter: wewang <wewang>
Component: BuildAssignee: Ben Parees <bparees>
Status: CLOSED ERRATA QA Contact: Wenjing Zheng <wzheng>
Severity: medium Docs Contact:
Priority: low    
Version: 3.11.0CC: aos-bugs
Target Milestone: ---   
Target Release: 3.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-11 07:21:36 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:

Description wewang 2018-07-04 07:01:26 UTC
Description of problem:
When implement s2i build with "--as-dockerfile=Dockerfile" not  "--as-dockerfile=./Dockerfile", command success and generated dockerfile, but did not create upload dir.

Version-Release number of selected component (if applicable):
s2i v1.1.11-14-g05cadb9

How reproducible:
always 

Steps to Reproduce:
1.Build a binary
2. Produce an docker file from s2i build
    $s2i build //github.com/openshift/nodejs-ex  openshift/nodejs-010-centos7
 --as-dockerfile=Dockerfile
3.According dockerfile content, if build success, should also had upload directory
 # Copying in source code
  COPY --chown=1001:0 upload/src /tmp/src

Actual results:
build success

Expected results:
should build failed and give error info 
Additional info:

Comment 1 Ben Parees 2018-07-05 17:08:01 UTC
PR: https://github.com/openshift/source-to-image/pull/901

Comment 2 wewang 2018-07-06 05:50:05 UTC
verified in s2i version
v1.1.11-16-ga02a8c3

Comment 4 errata-xmlrpc 2018-10-11 07:21:36 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-2018:2652