yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

** Also affects: nova/ocata
   Importance: Undecided
       Status: New

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

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

** Changed in: nova/ocata
       Status: New => In Progress

** Changed in: nova/ocata
     Assignee: (unassigned) => Matt Rabe (mdrabe)

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

Title:
  Evacuated instances that are deleted before the source host comes up
  causes cleanup not to happen

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) ocata series:
  In Progress

Bug description:
  Description
  ===========
  When an instance is evacuated to another host, the VM remains on the source host until it is brought back up and deleted by compute via _destroy_evacuated_instances.

  However if the VM that's created on the destination is deleted before
  the source host is brought back up, then _destroy_evacuated_instances
  won't reap the remains because it searches non-deleted records.

  Steps to reproduce
  ==================
  1. Deploy a VM.
  2. Bring the host the VM is on down.
  3. Evacuate the VM to a different host.
  4. Delete the VM from the destination.
  5. Bring the source host back up.

  The source remnants from the evacuation will not be cleaned up, but
  they should be.

  Suspect code is in the nova compute manager in
  _destroy_evacuated_instances:

  1. MigrationList.get_by_filters doesn't appear to return deleted migration records.
  2. {'deleted': False} is currently passed as the filter to _get_instances_on_driver.

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