Előd Illés a3f286f43d 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. Change-Id: I06d78c744fa75ae5f34c5cfa76bc3c9460767b84 Closes-Bug: #1713783 (cherry picked from commit a8ebf5f1aa)		2017-09-18 10:58:38 -04:00
..
tasks	Merge "Cleanup allocations on invalid dest node during live migration" into stable/pike	2017-09-15 22:19:13 +00:00
__init__.py	Remove conductor local api:s and 'use_local' config option	2016-10-18 14:26:06 +02:00
api.py	Merge "Remove translation of log messages"	2017-08-10 11:39:03 +00:00
manager.py	Set error state after failed evacuation	2017-09-18 10:58:38 -04:00
rpcapi.py	Default reservations=None in Cells v1 and conductor APIs	2017-07-14 12:25:58 +00:00