OpenStack Compute (nova)

  1. Series stein
  2. Bug #1833581
  3. Comment #25

Comment 25 for bug 1833581

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (stable/rocky)

Reviewed: https://review.opendev.org/687565
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=13bb7ed701121955ba015103c2e44429927e78d4
Submitter: Zuul
Branch: stable/rocky

commit 13bb7ed701121955ba015103c2e44429927e78d4
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
    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.

    Conflicts:
          nova/tests/unit/compute/test_compute_mgr.py
          nova/compute/manager.py

    Conflict due to Ia1b3ab0b66fdaf569f6c7a09510f208ee28725b2 and
    I020e7dc47efc79f8907b7bfb753ec779a8da69a1 is not in stable/rocky

    Change-Id: I856a3032c83fc2f605d8c9b6e5aa3bcfa415f96a
    Closes-Bug: #1833581
    (cherry picked from commit a1a735bc6efa40d8277c9fc5339f3b74f968b58e)
    (cherry picked from commit 06fd7c730172190d7bf7d52bc9062eecba8d7d27)
    (cherry picked from commit cb951cbcb246221e04a063cd7b5ae2e83ddfe6dd)