How to upgrade MAAS

Docs
1

General notes

  • Review PostgreSQL Requirements: MAAS 3.5 and later require PostgreSQL 14. Upgrade instructions here.
  • Upgrade Ubuntu if needed: Ensure you’re running Ubuntu 22.04 (Jammy) before upgrading MAAS. This is only relevant if you plan to install MAAS from packages. Snap-based installation does not require upgrading the base system.
  • Backup your data: Always create a backup before upgrading.
  • Multi-node setups: Upgrade rack nodes first, then region nodes.

Upgrade to MAAS 3.5

Upgrade Snap (region + rack)

sudo snap refresh maas --channel=3.5/stable

Upgrade package (PPA-based installations)

sudo apt-add-repository ppa:maas/3.5
sudo apt install maas

Upgrade packages from MAAS versions 2.9-3.3

  1. Upgrade PostgreSQL: If running PostgreSQL 12, upgrade to 14.
  2. Ensure Ubuntu 22.04 (Jammy):
    lsb_release -a
    If on Ubuntu 20.04, upgrade:
    sudo do-release-upgrade --allow-third-party
  3. Add PPA and Upgrade:
    sudo apt-add-repository ppa:maas/3.5
sudo apt install maas
  4. Verify Installation:
    maas --version

Upgrade packages from MAAS 2.8 or earlier

  1. Backup your system completely.
  2. Ensure Ubuntu 22.04 (see steps above).
  3. Add PPA and Upgrade:
    sudo apt-add-repository ppa:maas/3.5
sudo apt install maas
  4. If the upgrade fails, restore from backup and consider a fresh installation.

Upgrade to MAAS 3.4

Upgrade snap

sudo snap refresh maas --channel=3.4/stable

Upgrade package

sudo apt-add-repository ppa:maas/3.4
sudo apt install maas
  • Follow the same Ubuntu and PostgreSQL upgrade steps as above.

Upgrade to MAAS 3.3

Upgrade snap

sudo snap refresh maas --channel=3.3/stable

Upgrade packages

sudo apt-add-repository ppa:maas/3.3
sudo apt install maas
  • PostgreSQL 12 is deprecated in MAAS 3.3 and unsupported in 3.5. Upgrade to PostgreSQL 14 before proceeding.

Additional notes

Avoiding NTP conflicts

If you experience time synchronization issues:

sudo systemctl disable --now systemd-timesyncd

BMC migration issue (MAAS 3.3+)

Ensure unique BMC IP/username/password combinations before upgrading to avoid migration failures.

Verification steps

After upgrading, confirm MAAS is running correctly:

lsb_release -a  # Ensure Ubuntu version is correct
maas --version  # Verify MAAS version
2

This document is horribly out of date and needs to be refreshed by the MaaS team…
Things that are important are missing like, does the upgrade need to be step-wise or can you skip in-between versions?

1 Like
3

I agree with @dandruczyk.

The upgrade steps are currently in https://maas.io/docs/snap/3.1/ui/maas-installation and https://maas.io/docs/deb/3.1/cli/maas-installation

This page is currently the only obvious page for upgrading but only talks about upgrading old versions (which is handy and important, but should not be the main topic for this page).

1 Like
4

message received and understood. lemme see what i can do with this.

5

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.

6

Hi @billwear

What should be the procedure when upgrading a HA MAAS (3 nodes) cluster?

  1. Should I go ahead and upgrade all three nodes at the same time, or maybe go one by one?
  2. Should I stop MAAS services before doing the upgrade to avoid having a difference on the version during a period of time?
  3. If going one by one, should I expect them to be synchronized or out of sync during the upgrades?
  4. Is there a way to check the nodes are back into a quorum?
7

I would probably divide up the “Special Situations” section into multiple sub-sections so that when folx look at the Index of the page at the top, they can more easily recognize if they are in fact a Special Situation™.

Specifically, I’d make (what appears to be the only case?) a sub-section with its own heading.