Evacuated instances that are deleted before the source host comes up causes cleanup not to happen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Matt Rabe | ||
Ocata |
Fix Committed
|
Medium
|
Matt Rabe |
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_
However if the VM that's created on the destination is deleted before the source host is brought back up, then _destroy_
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_
1. MigrationList.
2. {'deleted': False} is currently passed as the filter to _get_instances_
Changed in nova: | |
assignee: | nobody → Dinesh Bhor (dinesh-bhor) |
Changed in nova: | |
status: | New → Confirmed |
Changed in nova: | |
assignee: | Matt Rabe (mdrabe) → Eric Fried (efried) |
Changed in nova: | |
assignee: | Eric Fried (efried) → Matt Rabe (mdrabe) |
tags: | added: evacuate |
Changed in nova: | |
importance: | Undecided → Medium |
Fix proposed to branch: master /review. openstack. org/467774
Review: https:/