yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1217222] Re: nova-compute keep reporting "Instance xxxx found in the hypervisor, but not in the database"

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Melanie Witt <1217222@xxxxxxxxxxxxxxxxxx>
Date: Tue, 08 Oct 2013 19:38:22 -0000
Reply-to: Bug 1217222 <1217222@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

*** This bug is a duplicate of bug 1190206 ***
    https://bugs.launchpad.net/bugs/1190206

** This bug has been marked a duplicate of bug 1190206
   Cleanup of deleted instance fails

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

Title:
  nova-compute keep reporting  "Instance xxxx found in the hypervisor,
  but not in the database"

Status in OpenStack Compute (Nova):
  New

Bug description:
  I'm working under Grizzly + CentOS.

  After several weeks work, my compute node keep reporting Errors like :
  ......
  2013-08-27 14:53:42.750 ERROR nova.compute.manager [req-5ad29824-ab32-40d3-a26c-cd1d050b8244 None None] Instance d47ea1c4-8731-4c92-9b3d-1475ad09e629 found in the hypervisor, but not in the database
  2013-08-27 14:53:42.750 ERROR nova.compute.manager [req-5ad29824-ab32-40d3-a26c-cd1d050b8244 None None] Instance a1d6391e-7e17-417c-94f2-ac0f9dba6dd4 found in the hypervisor, but not in the database
  ......

  
  While, instance is not active but exist in libvirt:

  virsh list --all
   Id    Name                           State
  ----------------------------------------------------
   -     instance-00000004              shut off
   -     instance-00000168              shut off
   -     instance-00001727              shut off
   -     instance-0000172f              shut off
   -     instance-00001730              shut off
   -     instance-00001731              shut off
   -     instance-00001732              shut off
   -     instance-00001733              shut off
   -     instance-00001734              shut off
   -     instance-00001735              shut off
   -     instance-00001736              shut off
   -     instance-00001737              shut off
   -     instance-00001754              shut off
   -     instance-00001755              shut off
   -     instance-00001756              shut off
   -     instance-00001757              shut off
   -     instance-00001758              shut off
   -     instance-00001759              shut off
   -     instance-0000175a              shut off
   -     instance-0000175b              shut off
   -     instance-0000175c              shut off
   -     instance-0000175d              shut off

  
  But, I have already set periodic_task _cleanup_running_deleted_instances running under reap mode：
  running_deleted_instance_action=reap
  running_deleted_instance_poll_interval=10
  running_deleted_instance_timeout=0

  
  Anyone know why ???

  Thanks.
  -chen

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