Bug 1252647

Summary:	new-app output for S2I incorrectly suggests you can run a build with start-build
Product:	OpenShift Container Platform	Reporter:	Erik M Jacobs <ejacobs>
Component:	oc	Assignee:	Fabiano Franz <ffranz>
Status:	CLOSED DUPLICATE	QA Contact:	Yanping Zhang <yanpzhan>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.0.0	CC:	jokerman, libra-bugs, libra-onpremise-devel, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-16 21:10: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 Erik M Jacobs 2015-08-12 00:53:03 UTC

oc new-app jboss-eap6-openshift~https://github.com/thoraxe/openshift3mlbparks.git
imagestreams/openshift3mlbparks
buildconfigs/openshift3mlbparks
deploymentconfigs/openshift3mlbparks
services/openshift3mlbparks
A build was created - you can run `oc start-build openshift3mlbparks` to start it.
Service "openshift3mlbparks" created at 172.30.169.206 with port mappings 8080->8080, 8443->8443.
Run 'oc status' to view your app.

oc version
oc v3.0.1.0-503-g7cc6deb
kubernetes v1.0.0


If I remember right, if I was to "start-build" after seeing this, I might possibly end up with *two* builds running because of the way OpenShift decides whether or not to run the first build.

We may want to remove that output from the client to prevent double-build issues.

Comment 2 Fabiano Franz 2015-08-16 21:10:36 UTC


*** This bug has been marked as a duplicate of bug 1248464 ***