e34fbb174c
When upgrading Nova, we sometimes hit an error where an old hypervisor that hasn’t been upgraded recently (for example due to broken hardware) is preventing Nova API from starting properly. This can be detected using the tool ``nova-status upgrade check`` to make sure that there are no ``nova-compute`` that are older than N-1 releases. This is already used in the Kolla Ansible upgrade task for Nova. However, this task uses the current ``nova-api`` container, so computes which will be too old after the upgrade are not caught. This patch changes Kolla Ansible so that the upgraded ``nova-api`` image is used to run the upgrade checks, allowing computes that will be too old to be detected before the upgrades are performed. Depends-On: https://review.opendev.org/c/openstack/kolla/+/878744 Closes-Bug: #1957080 Co-Authored-By: Pierre Riteau <pierre@stackhpc.com> Change-Id: I3a899411001834a0c88e37f45a756247ee11563d
11 lines
492 B
YAML
11 lines
492 B
YAML
---
|
|
fixes:
|
|
- |
|
|
When upgrading Nova to a new release, we use the tool ``nova-status upgrade
|
|
check`` to make sure that there are no ``nova-compute`` that are older than
|
|
N-1 releases. This was performed using the current ``nova-api`` container,
|
|
so computes which will be too old after the upgrade were not caught. Now
|
|
the upgraded ``nova-api`` container image is used, so older computes are
|
|
identified correctly.
|
|
`LP#1957080 <https://launchpad.net/bugs/1957080>`__
|