yahoo-eng-team team mailing list archive

[Chuck Short <chuck.short@xxxxxxxxxxxxx>]

I am not able to reproduce this at all on Grizzly.

** Changed in: nova (Ubuntu)
       Status: Triaged => 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/1012551

Title:
  Cannot delete instance in ERROR status

Status in OpenStack Compute (Nova):
  Fix Committed
Status in “nova” package in Ubuntu:
  Fix Released

Bug description:
  Hi

  I think there is a bug of nova .
  The situation is :

  When I try to boot a instance first time , it report spawning error ,
  The reason is My compute-node don't support kvm virtuallization , So I
  use qemu instead , Of course it work well after change . BUT when I
  try to delete the error instance , It cannot be deleted , stay at
  deleting .

  I found the reason is libvirt cannot find the error instance nova
  created before , The libvirt raise error when it try to create
  instance But store instance info into db , . So when we want to delete
  the error instance , the instance cannot be found by libvirt , So it
  cannot be destroy of course .

  Also found that , the Domain XML in two place .
  One is in /var/lib/nova/instance/instance-xxxxx/libvirt.xml which maybe create by nova I think
  The other is in /etc/libvirt/qemu/instance-xxxxx.xml which maybe create by libvirt I think

  I found the error instance's domain config xml only exist in  /var/lib/nova/instance/
  The active instance's xml in both  /var/lib/nova/instance/ and  /etc/libvirt/qemu/

  finally , I have to change the db manually so that this error instance
  record look like terminated . and it work .

  My openstack version :
  #nova-manage version
  2012.1 (2012.1-LOCALBRANCH:LOCALREVISION)


  Thank you

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