Bug 1384419

Summary:	The latest deployment is not shown on overview page if the deployment status is cancelled
Product:	OKD	Reporter:	Yanping Zhang <yanpzhan>
Component:	Management Console	Assignee:	Samuel Padgett <spadgett>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.x	CC:	aos-bugs, jforrest, mmccomas, xxia
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1389458 (view as bug list)		Environment:
Last Closed:	2016-12-09 21:51:05 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:
Bug Depends On:
Bug Blocks:	1389458

Description Yanping Zhang 2016-10-13 09:18:24 UTC

Description of problem:
Deploy a dc several times, and cancel the last deployment, check on overview page, it displays the previous active deployment, but the latest deployment is not shown.


Version-Release number of selected component (if applicable):
openshift v1.4.0-alpha.0+c728fe9 (latest origin-web-console, latest commit is 03b49b4, manually vendored)
kubernetes v1.4.0+776c994
etcd 3.1.0-alpha.1


How reproducible:
Always

Steps to Reproduce:
1.Deploy a dc several times, and cancel the last deployment
2.Check dc/deployments on overview page
3.

Actual results:
2.it displays the previous active deployment, but the latest deployment is not shown

Expected results:
2.The latest deployment should be shown on overview page.

Additional info:

Comment 1 Samuel Padgett 2016-10-13 13:22:50 UTC

I think it should just be an alert: "(!) Deployment #7 was cancelled."

Comment 2 Samuel Padgett 2016-10-13 14:17:15 UTC

Note that this is working as intended, although it is a change from 1.2.

Comment 3 Yanping Zhang 2016-10-14 02:17:51 UTC

(In reply to Samuel Padgett from comment #1)
> I think it should just be an alert: "(!) Deployment #7 was cancelled."

Yes, if possible, an alert would be better.

Comment 4 Samuel Padgett 2016-10-25 14:33:42 UTC

https://github.com/openshift/origin-web-console/pull/722

Comment 5 Xingxing Xia 2016-10-27 06:12:33 UTC

Tested against openshift v3.4.0.16+cc70b72, the PR is merged in.
Now it shows alert about the last cancelled/failed deployment (previous cancelled/failed deployment is replaced by the last). Looks good!

Comment 6 Xingxing Xia 2016-10-27 07:13:52 UTC

Hmm, the fix works for DC that has linked service, but for DC that has no service, there is no alert for its last cancelled/failed deployment.
DC that has linked service:
$ oc new-app centos/ruby-22-centos7~https://github.com/openshift/ruby-ex.git

DC that has no service:
$ oc run hello --image=openshift/hello-openshift

Comment 7 Samuel Padgett 2016-10-27 12:11:36 UTC

@Jessica, thoughts on this? It looks like we don't support any notifications for unserviced deployment configs.

Comment 8 Samuel Padgett 2016-10-27 15:39:42 UTC

I opened a separate bug for not seeing notifications for unserviced deployment configs. That's a general problem not specific to this fix.

https://bugzilla.redhat.com/show_bug.cgi?id=1389458

Comment 9 Xingxing Xia 2016-10-28 02:55:00 UTC

Thanks!