_init_instance recovery from failed in-progress resize leaves old records and allocations
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Triaged
|
Low
|
Unassigned |
Bug Description
This came up in review here:
https:/
And was confirmed in a functional test patch here:
https:/
There are some known things that get left behind when recovering a guest on the source host when the source compute service host crashes while the virt driver's migrate_
- the instance.
- the instance.new_flavor
- the instance.
The migration_context might be the only real issue there since it's used in the API for routing os-server-
Probably the bigger issue is the migration-based allocations don't get cleaned up. This means the source host allocations are still tracked against the migration record for the old flavor, and the dest host allocations for the new flavor are tracked by the instance, even though the instance isn't running on the dest host.
tags: | added: placement |
Marked as Low severity since this is extremely latent behavior.