...

1. Stop all magnum-services by adding the following keys to node-specific hiera, and then make sure to run puppet on the magnum hosts:

   1. magnum::conductor::enabled: false

   2. apache::service_ensure: 'stopped'

2. Run puppet with the 2023.1 modules/tags

3. Run apt dist-upgrade && apt autoremove

4. Run su -s /bin/sh -c "magnum-db-manage upgrade" magnum

5. Re-start magnum services by removing the keys added in step 1 and re-run puppet.

6. Check if a new Fedora CoreOS image is required, and if new public cluster templates should be deployed. I.e to support a newer k8s version
   1. The official documentation provides a nice bit of help with this.

Octavia

Octavia must be stopped for upgrades, and can thus be performed on all octavia-hosts at the same time. It might be an idea to keep one set of hosts stopped at old code in case of the need for a sudden roll-back.

1. Stop all octavia-services by adding the following keys to hiera, and then make sure to run puppet on the octavia hosts:

   1. octavia::housekeeping::enabled: false

   2. octavia::health_manager::enabled: false

   3. octavia::api::enabled: false

   4. octavia::worker::enabled: false

2. Do one of:

   1. Reinstall the node with 2023.1 modules/tags

   2. Run puppet with the 2023.1 modules/tags, Run apt-get dist-upgrade && apt-get autoremove, Run puppet

3. Run octavia-db-manage upgrade head


4. Re-start octavia services by removing the keys added in step 1 and re-run puppet.

5. Build a 2023.1-based octavia-image and upload to glance. Tag it and make octavia start to replace the amphora.

Horizon

1. Run puppet with the 2023.1 modules/tags
2. Add the following to the node-specific hiera file for horizon nodes:
   1. apache::mod::wsgi::package_name: 'libapache2-mod-wsgi-py3'
   2. apache::mod::wsgi::mod_path: '/usr/lib/apache2/modules/mod_wsgi.so'
3. run apt dist-upgrade && apt autoremove

4. Run puppet again
5. restart apache2