Matt Riedemann 68f7b95bdc Handle no allocations during migrate ... The CachingScheduler does not create allocations in the scheduler, so the assertion in the conductor migrate task that the instance will have allocations on the source node is incorrect. This removes the assertion and changes the error to a debug message. The related functional regression test is updated to show resize working with the CachingScheduler again. There are other places in the code, especially the compute and resource tracker, where we log errors if we can't find allocations and those likely need to be updated at some point, but it can happen in a follow up. Change-Id: I0bb2933c4ed7ed479206c9b06be7e30a2ec92f2a Closes-Bug: #1741307		2018-01-04 14:18:50 -05:00
..
__init__.py	Removed copyright from empty files	2014-02-27 14:27:54 +02:00
base.py	Create class hierarchy for tasks in conductor	2015-07-30 17:35:56 +03:00
live_migrate.py	Workaround missing RequestSpec.project_id when moving an instance	2017-12-20 09:16:28 -05:00
migrate.py	Handle no allocations during migrate	2018-01-04 14:18:50 -05:00