Bug 1393803

Summary: Source Configuration missing on bc editing page
Product: OpenShift Container Platform Reporter: Li Zhe <zhezli>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.4.0CC: aos-bugs, jforrest, jokerman, mmccomas, tdawson, zhezli
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
The build config editor now shows a message when there are no editable source types for a build config. Previously it displayed as a blank section in the editor.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-18 12:54:38 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:

Comment 1 Samuel Padgett 2016-11-10 15:46:27 UTC
https://github.com/openshift/origin-web-console/pull/855

The fix is to show a message saying there are no editable source types under source configuration in the build config editor. The reason is that the `binary.asFile` field is set on the CLI when you run `oc start-build --from-file` and does not make sense to edit from the web console. It will be changed again after any binary build run from the CLI with `--from-file` or `--from-dir`.

Comment 2 Samuel Padgett 2016-11-10 15:46:34 UTC
https://github.com/openshift/origin-web-console/pull/855

The fix is to show a message saying there are no editable source types under source configuration in the build config editor. The reason is that the `binary.asFile` field is set on the CLI when you run `oc start-build --from-file` and does not make sense to edit from the web console. It will be changed again after any binary build run from the CLI with `--from-file` or `--from-dir`.

Comment 3 Troy Dawson 2016-11-11 19:46:41 UTC
This has been merged into ocp and is in OCP v3.4.0.25 or newer.

Comment 7 errata-xmlrpc 2017-01-18 12:54:38 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-2017:0066