Comment 2 for bug 1848343
Revision history for this message
| Matt Riedemann (mriedem) wrote Re: MigrationTask rollback can leak allocations for a deleted server | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
I think we can claim this as a regression going back to migration-based allocations added in Queens. Looking at where a resize would fail during prep_resize in Pike, we call this method to remove the 'doubled up' allocations or the instance:
https:/
That's to remove the dest host provider from the allocations created by the scheduler.
In this case if the instance was deleted concurrently and had no allocations, we'd get here and return False:
https:/
And we'd log an error there and here in the resource tracker:
https:/
But we wouldn't leak any allocations for the deleted instance which is the bug we have since Queens when reverting the allocation swap and the instance is gone.