...
- Set
glance::sync_db: false
in a global hiera-file - Select which glance-server to upgrade first.
- In the node-specific hiera for this host you should set:
glance::api::enableenabled: false
followed by a puppet-run. This would stop the glance-api service on the host.
- In the node-specific hiera for this host you should set:
- Run puppet on the first host with the rocky modules/tags
- Run
apt dist-upgrade
- Run
glance-manage db expand
- Run
glance-manage db migrate
- Remove the
glance::api::enable: false
from the node-specific hiera, and run puppet again. This would re-start the glance api-server on this host.- Test that this api-server works.
- Upgrade the rest of the glance hosts (ie; step 3 + 4 for each of the remaining glance hosts)
- Run
glance-manage db_
contract
- Remove
glance::sync_db: false
in a global hiera-file
...
- Pick the first node, and run puppet with the rocky modules/tags
- Run
apt dist-upgrade
- Run
neutron-db-manage upgrade --expand
- Rocky will upgrade to FWaaS V2, run
neutron-db-manage --subproject neutron-fwaas upgrade head
to prepare the database - Restart neutron-server.service and rerun puppet
- Upgrade the rest of the API-nodes (repeating step 1, 2 and 5)
- When all API-nodes are upgraded, run
neutron-db-
mangemanage has_offline_migrations
- When the above command reports "
No offline migrations pending
" it is safe to: - Run
neutron-db-manage upgrade --contract
- When the above command reports "
...