diff options
| author | Roman Krček <roman.krcek@tietoevry.com> | 2024-09-05 18:11:53 +0200 |
|---|---|---|
| committer | Roman Krček <roman.krcek@tietoevry.com> | 2024-09-13 11:05:43 +0200 |
| commit | 41448f2077b5469bedd62fe4b96cb0aff6c60938 (patch) | |
| tree | b51404f578edb17460c9dce771afe0e681cedecb /etc/kolla/globals.yml | |
| parent | d62523f778f5d481b249bb904da864e86ee9d8a0 (diff) | |
| download | kolla-ansible-41448f2077b5469bedd62fe4b96cb0aff6c60938.tar.gz kolla-ansible-41448f2077b5469bedd62fe4b96cb0aff6c60938.zip | |
Refactor nova upgrade task
This is a prerequisite for patchset #924651
Nova runs checks before upgrading. A new nova_upgrade_checks container
is started for that purpose. This container uses the new nova-api
image, but the old config.json file. The image expects CA certificates
in a certain location, but due to the old config.json file, they will
not be present. This results in the container not trusting keystone SSL
certificate and the upgrade fails, since it can't connect. Moving the
config section before the checks ensures that the new container has
all the certificates it needs to connect to Keystone.
Also nova_enable_rolling_upgrade is no longed used, so there was no
point in keeping upgrade tasks split.
Change-Id: I44bf48fb86f639d7f0acb786392573ebfed7ee97
Signed-off-by: Roman Krček <roman.krcek@tietoevry.com>
Diffstat (limited to 'etc/kolla/globals.yml')
| -rw-r--r-- | etc/kolla/globals.yml | 12 |
1 files changed, 5 insertions, 7 deletions
diff --git a/etc/kolla/globals.yml b/etc/kolla/globals.yml index bb7b16c28..793127d29 100644 --- a/etc/kolla/globals.yml +++ b/etc/kolla/globals.yml @@ -608,13 +608,11 @@ workaround_ansible_issue_8743: yes # The number of fake driver per compute node #num_nova_fake_per_node: 5 -# The flag "nova_safety_upgrade" need to be consider when -# "nova_enable_rolling_upgrade" is enabled. The "nova_safety_upgrade" -# controls whether the nova services are all stopped before rolling -# upgrade to the new version, for the safety and availability. -# If "nova_safety_upgrade" is "yes", that will stop all nova services (except -# nova-compute) for no failed API operations before upgrade to the -# new version. And opposite. +# The "nova_safety_upgrade" controls whether the nova services +# are all stopped before rolling upgrade to the new version, +# for the safety and availability. If "nova_safety_upgrade" is "yes", +# that will stop all nova services (except nova-compute) for no failed +# API operations before upgrade to the new version. And opposite. #nova_safety_upgrade: "no" # Valid options are [ none, novnc, spice ] |