Matt Riedemann b5e6c389d7 Handle get_host_availability_zone error during reschedule ... If a build fails and reschedules to a cell conductor which does not have access to the API DB, the call to get_host_availability_zone will fail with a CantStartEngineError because it's trying to do an "up-call" to the API DB for host aggregate info. The reschedule fails and the instance is stuck in BUILD status without a fault injected for determining what went wrong. This change simply handles the failure and cleans up so the instance is put into a terminal (ERROR) state. Change-Id: I6bfa6fa767403fb936a6ae340b8687eb161732fc Partial-Bug: #1781286 (cherry picked from commit 38fb7f82ab)		2019-10-02 13:45:58 -04:00
..
tasks	Reject migration with QoS port from conductor if RPC pinned	2019-09-24 10:12:05 +02:00
__init__.py	Remove conductor local api:s and 'use_local' config option	2016-10-18 14:26:06 +02:00
api.py	Stop passing 'kwargs' to 'rebuild_instance'	2019-06-12 16:09:46 +01:00
manager.py	Handle get_host_availability_zone error during reschedule	2019-10-02 13:45:58 -04:00
rpcapi.py	Handle legacy request spec dict in ComputeTaskManager._cold_migrate	2019-09-24 14:36:01 -04:00