Bug 1433229 – Deploy from webconsole fails but rollout latest success

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1433229 - Deploy from webconsole fails but rollout latest success

Summary:	Deploy from webconsole fails but rollout latest success

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Management Console (Show other bugs)
Sub Component:
Version:	3.4.1
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jessica Forrester
QA Contact:	XiaochuanWang
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-03-17 02:27 EDT by yufchang
Modified:	2017-08-22 04:28 EDT (History)
CC List:	9 users (show)

See Also:
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 01:18:47 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHEA-2017:1716	normal	SHIPPED_LIVE	Red Hat OpenShift Container Platform 3.6 RPM Release Advisory	2017-08-10 05:02:50 EDT

Groups: None (edit)

Description yufchang 2017-03-17 02:27:27 EDT

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 06:09:01 EDT

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 01:58:02 EDT

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 11:20:42 EDT

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 11:26:14 EDT

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 15:33:20 EDT

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

Comment 10 yufchang 2017-04-20 02:55:48 EDT

Verify in OCP v3.6.39; Fixed!

Comment 12 errata-xmlrpc 2017-08-10 01:18:47 EDT

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

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