Public bug reported:
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://github.com/openstack/nova/blob/stable/liberty/nova/compute/manager.py#L817
nova-compute read migration record from db to get the evacuated instance and
then destroy it. It filters migration with status 'accepted'.
https://github.com/openstack/nova/blob/stable/liberty/nova/compute/manager.py#L2715
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.
** Affects: nova
Importance: Undecided
Assignee: lvdongbing (dbcocle)
Status: New
** Changed in: nova
Assignee: (unassigned) => lvdongbing (dbcocle)
--
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/1518200
Title:
instance not be destroyed after evacuate
Status in OpenStack Compute (nova):
New
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://github.com/openstack/nova/blob/stable/liberty/nova/compute/manager.py#L817
nova-compute read migration record from db to get the evacuated instance and
then destroy it. It filters migration with status 'accepted'.
https://github.com/openstack/nova/blob/stable/liberty/nova/compute/manager.py#L2715
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1518200/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
