Attempting to delete overcloud plan in GUI doesn't produce error message

[John Fulton]

While using the TripleO GUI, navigating to plans and then attempting to delete the overcloud plan, the GUI hung with a "Deleting overcloud…" message. I saw it hang there for ~5 minutes, and I think the correct behaviour would have been for it to produce an error message. I had originally deployed the overcloud, not with the GUI, but with the CLI using the default 2-node stack (`openstack overcloud deploy --templates`). So I think there should be an error messages because noone should be able to delete a plan if there's an overcloud attached to it.

I did see an error message in in the web console however:

16:43:07.672 Error deleting plan MistralApiService.runAction Object { status: "Action ERROR", message: "Failed to run action [action_ex_id=…" } 1 tripleo_ui.js:48994:9
 error http://10.9.76.25:3000/tripleo_ui.js:48994:9
 dispatch/< http://10.9.76.25:3000/tripleo_ui.js:49112:17
 dispatch http://10.9.76.25:3000/tripleo_ui.js:49105:8
 Logger/</_this3[fn] http://10.9.76.25:3000/tripleo_ui.js:49066:17
 deletePlan/</< http://10.9.76.25:3000/tripleo_ui.js:77348:10
 tryCatchReject http://10.9.76.25:3000/tripleo_ui.js:48251:29
 runContinuation1 http://10.9.76.25:3000/tripleo_ui.js:48210:5
 makePromise/Rejected.prototype.when http://10.9.76.25:3000/tripleo_ui.js:48031:5
 makePromise/Pending.prototype.run http://10.9.76.25:3000/tripleo_ui.js:47889:6
 __WEBPACK_AMD_DEFINE_RESULT__</Scheduler.prototype._drain http://10.9.76.25:3000/tripleo_ui.js:48402:5
 Scheduler/this.drain http://10.9.76.25:3000/tripleo_ui.js:48367:5
 run http://10.9.76.25:3000/tripleo_ui.js:46400:5

So I think it's basically do the right thing, but it should be more user friendly to tell me that it won't delete the plan and why.

Here are the versions I have. I had deployed the undercloud with tripleo-quckstart with master on Dec 8th around 3 PM (less than two hours ago).

[stack@undercloud ~]$ rpm -qa | grep tripleo
puppet-tripleo-6.0.0-0.20161204023935.77c1ca1.el7.centos.noarch
openstack-tripleo-common-5.5.1-0.20161201030354.76b1e81.el7.centos.noarch
openstack-tripleo-validations-5.2.1-0.20161125141845.6f90fbe.el7.centos.noarch
openstack-tripleo-image-elements-6.0.0-0.20161202172224.57a19a7.el7.centos.noarch
openstack-tripleo-puppet-elements-6.0.0-0.20161204020556.c3d4c61.el7.centos.noarch
python-tripleoclient-5.5.1-0.20161202172459.73756fc.el7.centos.noarch
openstack-tripleo-0.0.1-0.20161201152040.887a1e6.el7.centos.noarch
openstack-tripleo-heat-templates-6.0.0-0.20161202212111.a23ad11.el7.centos.noarch
openstack-tripleo-ui-2.0.0-0.20161130162727.b9ac332.el7.centos.noarch
[stack@undercloud ~]$

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE