Matt Riedemann 7ff71e6b87 Create instance action when burying in cell0 ... Change I8742071b55f018f864f5a382de20075a5b444a79 in Ocata moved the creation of the instance record from the API to conductor. As a result, the "create" instance action was only being created in conductor when the instance is created in a non-cell0 database. This is a regression because before that change when a server create would fail during scheduling you could still list instance actions for the server and see the "create" action but that was lost once we started burying those instances in cell0. This fixes the bug by creating the "create" action in the cell0 database when burying an instance there. It goes a step further and also creates and finishes an event so the overall action message shows up as "Error" with the details about where the failure occurred in the event traceback. A short release note is added since a new action event is added here (conductor_schedule_and_build_instances) rather than re-use some kind of event that we could generate from the compute service, e.g. compute__do_build_and_run_instance. Change-Id: I1e9431e739adfbcfc1ca34b87e826a516a4b18e2 Closes-Bug: #1852458 (cherry picked from commit f2608c9117) (cherry picked from commit 6484d9ff5b)		2020-06-10 16:37:33 +00:00
..
tasks	Merge "Update instance.availability_zone during live migration"	2019-03-13 23:25:11 +00:00
__init__.py	Remove conductor local api:s and 'use_local' config option	2016-10-18 14:26:06 +02:00
api.py	In Python3.7 async is a keyword [1]	2018-07-20 12:21:34 -04:00
manager.py	Create instance action when burying in cell0	2020-06-10 16:37:33 +00:00
rpcapi.py	Handle legacy request spec dict in ComputeTaskManager._cold_migrate	2019-09-26 11:00:11 -04:00