Upgrade your MAAS setup using this guide. Don't forget to consult the installation notes at the end.
Before updating to MAAS 3.4, keep in mind that PostgreSQL 12 support is being phased out. We recommend upgrading to PostgreSQL 14 beforehand.
If you're running MAAS versions 2.9 to 3.3, first check the Ubuntu version with lsb_release -a. Look for "22.04" as the release and "Jammy" as the codename.
Next, update Ubuntu, if needed. If you're on Ubuntu 20.04 LTS, move to 22.04 LTS using:
sudo do-release-upgrade --allow-third-party
You can safely follow the upgrade prompts, sticking to the default responses. When asked to reboot, restart the machine. When it reboots, double-check the Ubuntu version with lsb_release -a. The codename should now be "jammy."
Upgrading from MAAS 2.8 or lower? Proceed with caution; this is untested, so start by completely backing up your MAAS server.
Once that's done, add the PPA (ignore any errors here):
sudo apt-add-repository ppa:maas/3.4
Perform the upgrade, using this command and sticking to default answers:
sudo do-release-upgrade --allow-third-party
Confirm the upgrade using lsb_release -a (look for "22.04" and "Jammy"), and verify the MAAS version as "3.4."
Failed? Restore from your backup and consider a fresh install on separate hardware.
When installing MAAS on Ubuntu, there can be conflicts between the existing NTP client, systemd-timesyncd, and the NTP client/server provided by MAAS, chrony. This can lead to time synchronization issues, especially if MAAS is configured with different upstream NTP servers than the ones used by systemd-timesyncd. To avoid conflicts, users can manually disable and stop systemd-timesyncd using the following command:
sudo systemctl disable --now systemd-timesyncd
Also note that support for PostgreSQL 12 has been deprecated in MAAS 3.3 and will be discontinued in MAAS 3.5.