Page History

...

1. Set glance::sync_db: false in a global hiera-file
2. Select which glance-server to upgrade first.
   1. 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.
3. Run puppet on the first host with the rocky modules/tags
4. Run apt dist-upgrade
5. Run glance-manage db expand
6. Run glance-manage db migrate
7. 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.
   1. Test that this api-server works.
8. Upgrade the rest of the glance hosts (ie; step 3 + 4 for each of the remaining glance hosts)
9. Run glance-manage db_contract
10. Remove glance::sync_db: false in a global hiera-file

...

1. Pick the first node, and run puppet with the rocky modules/tags
2. Run apt dist-upgrade
3. Run neutron-db-manage upgrade --expand
4. Rocky will upgrade to FWaaS V2, run neutron-db-manage --subproject neutron-fwaas upgrade head to prepare the database
5. Restart neutron-server.service and rerun puppet
6. Upgrade the rest of the API-nodes (repeating step 1, 2 and 5)
7. When all API-nodes are upgraded, run neutron-db-mange manage has_offline_migrations
   1. When the above command reports "No offline migrations pending" it is safe to:
   2. Run neutron-db-manage upgrade --contract

...