commit f2608c91175411ec7c2604035adb39306d7e607e
Author: Matt Riedemann <email address hidden>
Date: Wed Nov 13 15:03:27 2019 -0500
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.
Reviewed: https:/ /review. opendev. org/694165 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=f2608c91175 411ec7c2604035a db39306d7e607e
Committed: https:/
Submitter: Zuul
Branch: master
commit f2608c91175411e c7c2604035adb39 306d7e607e
Author: Matt Riedemann <email address hidden>
Date: Wed Nov 13 15:03:27 2019 -0500
Create instance action when burying in cell0
Change I8742071b55f018 f864f5a382de200 75a5b444a79 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 schedule_ and_build_ instances) rather than _do_build_ and_run_ instance.
added here (conductor_
re-use some kind of event that we could generate from the
compute service, e.g. compute_
Change-Id: I1e9431e739adfb cfc1ca34b87e826 a516a4b18e2
Closes-Bug: #1852458