[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
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/1474772
Title:
updating incorrect resource during migration
Status in OpenStack Compute (nova):
Expired
Bug description:
In revert-resize method, migration.status changed to "reverted" in func
revert_resize on dest node, and instance's host will be set in
finish_revert_resize on source node.
If an update available resource called during this time in source node, the
resource of vm will free in source node too (include mem, cpu and pci).
I think migration.status should be set only after instance's host changed.
In resize-confirm method, resource is freed in function drop_move_claim. But
if the vm migrate in 1 min, the uuid might recored in tracked_instances but not
tracked_migrations.
drop_move_claim should consider this situation.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1474772/+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
