nova/nova/api
Dan Smith e8b079a91e Add service version check workaround for FFU
We recently added a hard failure to nova service startup for the case
where computes were more than one version old (as indicated by their
service record). This helps to prevent starting up new control
services when a very old compute is still running. However, during an
FFU, control services that have skipped multiple versions will be
started and find the older compute records (which could not be updated
yet due to their reliance on the control services being up) and refuse
to start. This creates a cross-dependency which is not resolvable
without hacking the database.

This patch adds a workaround flag to allow turning that hard fail into
a warning to proceed past the issue. This less-than-ideal solution
is simple and backportable, but perhaps a better solution can be
implemented for the future.

Related-Bug: #1958883

Change-Id: Iddbc9b2a13f19cea9a996aeadfe891f4ef3b0264
(cherry picked from commit 7d2e481589)
(cherry picked from commit 3a5f8924ff)
2022-06-01 17:37:12 +00:00
..
metadata Remove six.text_type (1/2) 2020-12-13 11:25:31 +00:00
openstack Add service version check workaround for FFU 2022-06-01 17:37:12 +00:00
validation libvirt: Wire up 'os_secure_boot' property 2021-03-09 15:56:18 +00:00
__init__.py
auth.py Stop using NoAuthMiddleware in tests 2019-10-14 11:43:52 -05:00
compute_req_id.py Migrate to oslo request_id middleware - mv 2.46 2017-05-27 10:11:44 +00:00
wsgi.py trivial: Remove remaining '_LE' instances 2020-05-18 16:52:20 +01:00