← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 2085975] [NEW] Compute fails to clean up after evacuated instance if the evacuation still in progress

 

Public bug reported:

Reproduce:
* have a two node devstack hostA, hostB both with simple local storage
* start an instance on hostA
* inject a sleep in nova.virt.driver.rebuild to simulate that rebuild take time
* stop hostA
* evacuate the VM 
* while the evacuation is still in progress on hostB start up hostA

Actual:
hostA will try to check if the VM is using shared storage and sends an RPC call to the instance.host as that is not yet set to the destination the RPC call hits hostA that is still in init_host so the RPC never answered and hostA'a destroy_evacuated_instances call will get a MessagingTimeout exception. That is logged and then ignored. But nova defaults the shared_storage flag to true so in this case the local instance dir is not cleaned.

Expected:
hostA sends the RPC call to hostB that responds and the local instance dir on hostkA is cleaned up.

** Affects: nova
     Importance: Medium
     Assignee: Balazs Gibizer (balazs-gibizer)
         Status: New


** Tags: compute evacuate race-condition

** Changed in: nova
     Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)

** Tags added: compute evacuate race-condition

** Changed in: nova
   Importance: Undecided => Medium

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

Title:
  Compute fails to clean up after evacuated instance if the evacuation
  still in progress

Status in OpenStack Compute (nova):
  New

Bug description:
  Reproduce:
  * have a two node devstack hostA, hostB both with simple local storage
  * start an instance on hostA
  * inject a sleep in nova.virt.driver.rebuild to simulate that rebuild take time
  * stop hostA
  * evacuate the VM 
  * while the evacuation is still in progress on hostB start up hostA

  Actual:
  hostA will try to check if the VM is using shared storage and sends an RPC call to the instance.host as that is not yet set to the destination the RPC call hits hostA that is still in init_host so the RPC never answered and hostA'a destroy_evacuated_instances call will get a MessagingTimeout exception. That is logged and then ignored. But nova defaults the shared_storage flag to true so in this case the local instance dir is not cleaned.

  Expected:
  hostA sends the RPC call to hostB that responds and the local instance dir on hostkA is cleaned up.

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



Follow ups