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

Bug 1433229

Summary:	Deploy from webconsole fails but rollout latest success
Product:	OpenShift Container Platform	Reporter:	yufchang <yufchang>
Component:	Management Console	Assignee:	Jessica Forrester <jforrest>
Status:	CLOSED ERRATA	QA Contact:	XiaochuanWang <xiaocwan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.4.1	CC:	aos-bugs, jokerman, mfojtik, mmccomas, spadgett, tdawson, xtian, yapei, yufchang
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: The web console had not been updated to use new API endpoints that could resolve ImageStream references at the time of a rollout. Consequence: DeploymentConfigs using an image change trigger with the automatic option turned off could not be manually deployed from the web console. Fix: The web console now uses the deploymentconfigs/instantiate API endpoint to trigger new manual deployments. Result: DeploymentConfigs using an image change trigger with the automatic option turned off can be manually deployed from the web console using the "Deploy" action.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-10 05:18:47 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 yufchang 2017-03-17 06:27:27 UTC

Description of problem:
Using the same DC, Deploy fails when using "Deploy" on web console, but succeed when using rollout latest

Version-Release number of selected component (if applicable):
kubernetes v1.4.0+776c994
Server https://api.ded-stg2-aws.openshift.com:443
openshift v3.4.1.10


How reproducible:
Always

Steps to Reproduce:
1.oc new-app -f https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/application-template.json
2.oc start-build frontend
3.After build complete, "Deploy" on the web console;
4. oc rollout latest frontend

Expected Result
3. Success in deployment;
4. Success in deployment;

Actual Result:
3. failed

It seemed that "deploy" on webconsole is not using the right command.
please confirm , thanks.



Additional info:

Comment 1 Michal Fojtik 2017-03-17 10:09:01 UTC

Can you please provide the error it fails with in webconsole? A deployer log, events, anything that can tell us why the deploy failed.

Comment 2 zhou ying 2017-03-20 05:58:02 UTC

I guess the root is "automatic": false, on webconsole , the deploy still use 'oc deploy ... --latest' command , we should use 'oc rollout latest' .

Comment 6 Jessica Forrester 2017-04-18 15:20:42 UTC

We never switched to creating a DeploymentRequest and using deploymentconfigs/instantiate, will be fixing that in https://github.com/openshift/origin-web-console/pull/1434/files

Comment 7 Jessica Forrester 2017-04-18 15:26:14 UTC

also the CLI command we reference in the console in the DC Triggers section was already updated, in master it tells the user to run oc rollout latest

Comment 8 Troy Dawson 2017-04-19 19:33:20 UTC

This has been merged into ocp and is in OCP v3.6.39 or newer.

Comment 10 yufchang 2017-04-20 06:55:48 UTC

Verify in OCP v3.6.39; Fixed!

Comment 12 errata-xmlrpc 2017-08-10 05:18:47 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/RHEA-2017:1716