Előd Illés 604954a70a Set error state after failed evacuation ... When evacuation fails with NoValidHost, the migration status remains 'accepted' instead of 'error'. This causes problem in case the compute service starts up again and looks for evacuations with status 'accepted', as it then removes the local instances for those evacuations even though the instance was never actually evacuated to another host. Conflicts: nova/conductor/manager.py NOTE(mriedem): The conflict is due to not having change I6590f0eda4ec4996543ad40d8c2640b83fc3dd9d in Ocata. Change-Id: I06d78c744fa75ae5f34c5cfa76bc3c9460767b84 Closes-Bug: #1713783 (cherry picked from commit a8ebf5f1aa) (cherry picked from commit a3f286f43d)		2018-04-17 12:24:41 -04:00
..
tasks	Remove mox from tests/unit/conductor/tasks/test_live_migrate.py(3)	2016-10-01 23:19:35 +09:00
__init__.py	move all tests to nova/tests/unit	2014-11-12 15:31:08 -05:00
test_conductor.py	Set error state after failed evacuation	2018-04-17 12:24:41 -04:00