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:
I think it should just be an alert: "(!) Deployment #7 was cancelled."
Note that this is working as intended, although it is a change from 1.2.
(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.
https://github.com/openshift/origin-web-console/pull/722
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!
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
@Jessica, thoughts on this? It looks like we don't support any notifications for unserviced deployment configs.
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
Thanks!