Comment 4 for bug 1941819
Revision history for this message
| Balazs Gibizer (balazs-gibizer) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
First I tried to reproduce the issue on master. But it turned out that instance.flavor is not lazy loaded at all in the nova-compute any more after [1] added a instance.flavor call as part of the compute API live_migrate[2] call in the block_accelerator decorator[3]. This run in the nova-api service a lot before the live migration hits the compute service.
Right now on master there is no double lazy load on the instance during the live migration so the problem cannot be reproduced there any more. It has been fixed by accident since Ussuri. The older than Ussuri nova branches are in extended maintenance mode [4]. You can still propose fixes but there won't be any point release out from Stein any more.
I think fix that you can try is to simply trigger the instance.flavor lazy load before the _live_migration() spawns the new thread.
[1] https:/
[2] https:/
[3] https:/
[4] https:/