yahoo-eng-team team mailing list archive

[Alfred Shen <alfredcs@xxxxxxxxx>]

Public bug reported:

When a VM is in a bad status, there's no effective way to delete it from
CLI/API even after reset-state. The only known option is to delete it
from MySql tables. in Kilo release following Nova tables will need to be
touched which is inconvenient and could post a risk. Would suggest to
come up with a tool to clean up a dysfunctional VM without touching
MySql tables.

Entries to be delete in following order

nova.instance_info_caches
nova.block_device_mapping
nova.instance_actions_events
nova.instance_actions
nova.instance_system_metadata
nova.instances

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1444683

Title:
  Still can't delete an VM in bad status from CLI/API on Kilo release

Status in OpenStack Compute (Nova):
  New

Bug description:
  When a VM is in a bad status, there's no effective way to delete it
  from CLI/API even after reset-state. The only known option is to
  delete it from MySql tables. in Kilo release following Nova tables
  will need to be touched which is inconvenient and could post a risk.
  Would suggest to come up with a tool to clean up a dysfunctional VM
  without touching MySql tables.

  Entries to be delete in following order

  nova.instance_info_caches
  nova.block_device_mapping
  nova.instance_actions_events
  nova.instance_actions
  nova.instance_system_metadata
  nova.instances

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