Eric Fried 1a7be0d62e Don't populate resources for not-yet-migrated inst ... Per the referenced bug, it is possible for update_available_resource to race with a migration such that the migration record exists, but the instance's migration context doesn't. In such cases we shouldn't try to track the instance's assigned resources on this host (because there aren't any yet). Change-Id: I69f99adfa8c91b50086052ca1b15c55e86ed614d Closes-Bug: #1849165 (cherry picked from commit 80385a22ee)		2019-10-22 10:10:36 -05:00
..
functional	Don't populate resources for not-yet-migrated inst	2019-10-22 10:10:36 -05:00
unit	Merge "Fix exception translation when creating volume" into stable/train	2019-10-21 18:50:20 +00:00
__init__.py	…
fixtures.py	Merge "Move HostNameWeigher to a common fixture"	2019-09-25 23:11:26 +00:00
json_ref.py	Transform instance.exists notification	2018-06-05 12:51:30 +00:00