Comment 8 for bug 1846820

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

Reviewed: https://review.opendev.org/c/openstack/nova/+/852901
Committed: https://opendev.org/openstack/nova/commit/232684b44022f1bc4d72b07045900780de456e63
Submitter: "Zuul (22348)"
Branch: master

commit 232684b44022f1bc4d72b07045900780de456e63
Author: Dan Smith <email address hidden>
Date: Thu Aug 11 10:18:25 2022 -0700

    Avoid n-cond startup abort for keystone failures

    Conductor creates a placement client for the potential case where
    it needs to make a call for certain operations. A transient network
    or keystone failure will currently cause it to abort startup, which
    means it is not available for other unrelated activities, such as
    DB proxying for compute.

    This makes conductor test the placement client on startup, but only
    abort startup on errors that are highly likely to be permanent
    configuration errors, and only warn about things like being unable
    to contact keystone/placement during initialization. If a non-fatal
    error is encountered at startup, later operations needing the
    placement client will retry initialization.

    Closes-Bug: #1846820
    Change-Id: Idb7fcbce0c9562e7b9bd3e80f2a6d4b9bc286830