VM instance is not automaticaly removed from table after completing the deletion of an instance that was in error state

[Gustavo Knüppe]

When you terminate an instance that is in error state, Horizon scheduled the task to terminate instance and shows "deleting.." description on Task column but no auto-refresh occurs.. as a result, the instance is not removed from the table after completing the deletion. A manual page refresh is required to remove the instance from the Table.

[Cindy Lu (clu-m)]

Hi, I just tested it out today, and it seems to be working - no manual page refresh needed.

[Cindy Lu (clu-m)]

nvm, i still see the behavior inconsistently :)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/73478

[tinytmy (tangmeiyan77)]

How to make a error instance:
1.Change libvirt_type=oooo
2.then restart nova-compute
3.launch a instance

Then terminate the instance,it will not auto-refresh。

[OpenStack Infra (hudson-openstack)]

Change abandoned by Julie Pichon (<email address hidden>) on branch: master
Review: https://review.openstack.org/73478
Reason: I agree with Timur's assessment. I tried to test the patch a while ago, but had difficulties reproducing the problem and the unit test appeared to pass even after removing the fix. This has the potential to reintroduce potentially dangerous bugs like infinite polling (see bug 948419), and in general, I agree it seems like too broad a solution for a small, specific issue.

Since the patch hasn't seen activity for several months, marking as Abandoned and releasing the bug. It might be worthwhile checking first if the problem still exist, considering all the JavaScript/bootstrap changes that have gone through since then.

[Richard Jones (r1chardj0n3s)]

I was unable to reproduce this bug.

[Launchpad Janitor (janitor)]

[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.]