instance is not destroyed on source host after a successful evacuate
Bug #1518200 reported by
lvdongbing
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
lvdongbing | ||
Liberty |
Fix Released
|
Medium
|
Sylvain Bauza |
Bug Description
After evacuate an instance to a new host successfully, then start the old host's nova-compute, bug the old instance not be destroyed as expected.
See following code:
https:/
nova-compute read migration record from db to get the evacuated instance and then destroy it. It filters migration with status 'accepted'.
https:/
After successfully evacuate instance, status of migration will change to 'done' from 'accepted'
So, I think we should modify 'accepted' to 'done' when filter migration record.
Changed in nova: | |
assignee: | nobody → lvdongbing (dbcocle) |
Changed in nova: | |
importance: | Undecided → Medium |
tags: | added: compute rebuild |
summary: |
- instance not be destroyed after evacuate + instance is not destroyed on source host after a successful evacuate |
Changed in nova: | |
assignee: | lvdongbing (dbcocle) → Sylvain Bauza (sylvain-bauza) |
tags: | added: liberty-backport-potential |
Changed in nova: | |
assignee: | Sylvain Bauza (sylvain-bauza) → lvdongbing (dbcocle) |
tags: |
added: evacuate in-stable-liberty removed: liberty-backport-potential |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/250101
Review: https:/