...
- Set
apache::service_ensure: 'stopped'
in hiera for the node that you are upgrading - Run puppet with the 2023.1 modules/tags, run apt-get dist-upgrade, and run puppet again
- Run
keystone-manage doctor
and ensure nothing is wrong - Run
keystone-manage db_sync --expand
- Returns nothing
- At this point, you may restart apache2 on this node
- Remove the
apache::service_ensure: 'stopped'
previously set in hiera.
- Remove the
- Upgrade keystone on the other nodes, one at a time
- Basically run step 1, 2 and 5 on the other nodes
- When all nodes are upgraded, perform the final DB sync
keystone-manage db_sync --contract
Glance
To upgrade glance without any downtime you would need to follow the following procedure:
- Select which glance-server to upgrade first.
- In the node-specific hiera for this host you should set:
apache::service_ensure: 'stopped'
- In the node-specific hiera for this host you should set:
- Run puppet with the 2023.1 modules/tags, run apt-get dist-upgrade, and run puppet again
- Remove the
apache::service_ensure: 'stopped'
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 2 for each of the remaining glance hosts)