If the compute service is restarted while build requests are
executing the instance_claim or waiting for the COMPUTE_RESOURCE_SEMAPHORE
then those instances will be stuck forever in BUILDING state. If the instance
already finished instance_claim then instance.host is set and when the
compute restarts the instance is put to ERROR state.
This patch changes compute service startup to put instances into
ERROR state if they a) are in the BUILDING state, and b) have
allocations on the compute resource provider, but c) do not have
instance.host set to that compute.
Change-Id: I856a3032c83fc2f605d8c9b6e5aa3bcfa415f96a
Closes-Bug: #1833581
(cherry picked from commit a1a735bc6efa40d8277c9fc5339f3b74f968b58e)
Reviewed: https:/ /review. opendev. org/687216 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=06fd7c73017 2190d7bf7d52bc9 062eecba8d7d27
Committed: https:/
Submitter: Zuul
Branch: stable/train
commit 06fd7c730172190 d7bf7d52bc9062e ecba8d7d27
Author: Balazs Gibizer <email address hidden>
Date: Fri Jun 21 16:48:14 2019 +0200
Error out interrupted builds
If the compute service is restarted while build requests are RESOURCE_ SEMAPHORE
executing the instance_claim or waiting for the COMPUTE_
then those instances will be stuck forever in BUILDING state. If the instance
already finished instance_claim then instance.host is set and when the
compute restarts the instance is put to ERROR state.
This patch changes compute service startup to put instances into
ERROR state if they a) are in the BUILDING state, and b) have
allocations on the compute resource provider, but c) do not have
instance.host set to that compute.
Change-Id: I856a3032c83fc2 f605d8c9b6e5aa3 bcfa415f96a 8277c9fc5339f3b 74f968b58e)
Closes-Bug: #1833581
(cherry picked from commit a1a735bc6efa40d