yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxx>]

Looks like this is implemented with commit [1] and available as CLI
command "nova force-delete <instance>" [2].

[1] https://git.openstack.org/cgit/openstack/nova/commit/?id=71b7298788045d4832dd8ec44cba3785955aa847
[2] http://docs.openstack.org/cli-reference/nova.html#nova-force-delete

** Changed in: nova
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/972320

Title:
  allow force terminate of instances

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  This is a small feature request really.

  It would be nice to have an extra flag or command to allow a "force
  terminate".

  I am thinking of cases like this:
  https://answers.launchpad.net/nova/+question/191046

  The admin could do with an operation to forcably update the DB to say
  the image is no longer on the system. We should not force people to
  edit the DB by hand. Of course, this should never happen, but a common
  cause is miss-configuration of the system.

  It would also be good to find out when a hypervisor appears to be out
  of sync with the database and allow an admin to go and solve that
  issue, rather than having to search around the logs and check the
  actual hypervisor. Perhaps use the notification system to notify there
  is a problem on the hypervisor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/972320/+subscriptions