Bug 1463170 - [free][free-int]No detailed build failure reason when using incorrect runtime image
[free][free-int]No detailed build failure reason when using incorrect runtime...
Product: OpenShift Online
Classification: Red Hat
Component: Build (Show other bugs)
Unspecified Unspecified
medium Severity low
: ---
: ---
Assigned To: Cesar Wong
Wenjing Zheng
Depends On:
  Show dependency treegraph
Reported: 2017-06-20 05:58 EDT by Wenjing Zheng
Modified: 2017-06-23 17:34 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-06-23 17:34:36 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Wenjing Zheng 2017-06-20 05:58:02 EDT
Description of problem:
Build failure reason is not detailed when using incorrect runtime image:
$ oc get builds
NAME                         TYPE      FROM          STATUS                           STARTED         DURATION
extended-build-from-repo-1   Source    Git@7323f1a   Failed (GenericS2IBuildFailed)   4 minutes ago   1m26s

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a project
2. Create buildconfig via tempate
a.wget <https://raw.githubusercontent.com/wzheng1/test-for-s2i-extendbuild/master/extended-bc-scripts-in-repo.json>
b. Edit to use incorrect runtime image
kind: DockerImage
name: **docker.io/uptoknow/123extendedbuild_runtime:latest**
3. Build with this template
4. Check build status

Actual results:
As description

Expected results:
It should show runtime image error like before.

Additional info:
Comment 1 Ben Parees 2017-06-23 17:34:36 EDT
since the extended build feature is deprecated (in favor of chained builds), we won't be fixing this.

Note You need to log in before you can comment on or make changes to this bug.