How to upgrade MAAS

Docs
#1

This article gives instructions for upgrading your MAAS installation. Please also check the installation notes at the end of this document.

How to upgrade a snap to MAAS 3.3

Note that support for PostgreSQL version 12 is deprecated for MAAS version 3.3, and will be discontinued in MAAS 3.5. We recommend upgrading to PostgreSQL version 14 before installing MAAS 3.3.

To upgrade from a earlier snap version to the 3.3 snap (using a region+rack configuration):

  1. Enter the following command:
sudo snap refresh --channel=3.3 maas
  1. Enter your account password.

The snap will refresh from the 3.3 channel. You will not need to re-initialise MAAS.

If you are using a multi-node maas deployment with separate regions and racks, you should first run the upgrade command above for rack nodes, then for region nodes.

How to upgrade MAAS 2.9++ to MAAS 3.3

Note that support for PostgreSQL version 12 is deprecated for MAAS version 3.3, and will be discontinued in MAAS 3.5. We recommend upgrading to PostgreSQL version 14 before installing MAAS 3.3.

If you are running MAAS 3.2 through MAAS 2.9, you can upgrade directly to MAAS 3.3 with the following procedure:

  1. Check whether the target system is running Ubuntu 22.04 LTS:
lsb_release -a

The response should look something like this:

Distributor ID:	Ubuntu
Description:	Ubuntu xx.yy
Release:	xx.yy
Codename:	$RELEASE_NAME

The required “xx.yy” for MAAS 3.3 is “22.04,” code-named “Jammy”.

  1. If you are currently running Ubuntu focal 20.04 LTS, Upgrade to Jammy 22.04 LTS:
sudo do-release-upgrade --allow-third-party

  1. Accept the defaults for any questions asked by the upgrade script.

  2. Reboot the machine when requested.

  3. Check whether the upgrade was successful:

lsb_release -a

A successful upgrade should respond with output similar to the following:

Distributor ID:	Ubuntu
Description:	Ubuntu 22.04(.nn) LTS
Release:	22.04
Codename:	jammy

How to upgrade MAAS 2.8-- to MAAS 3.3

If you’re upgrading from MAAS version 2.8 or lower to version 3.3, try the fooling procedure. While the this procedure should work, note that they it’s untested. Use at your own risk.

  1. Back up your MAAS server completely with your favourite tools and media.

  2. Add the MAAS 3.3 PPA to your repository list; ignore any apparent error messages:

sudo apt-add-repository ppa:maas/3.3
  1. Upgrade the release; answer any questions with the default values:
sudo do-release-upgrade --allow-third-party
  1. Check whether your upgrade has been successful:
lsb_release -a

If the upgrade was successful, this command should yield output similar to the following:

No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04(.nn) LTS
Release:	22.04
Codename:	jammy
  1. Check your running MAAS install (by looking at the information on the bottom of the machine list) to make sure you’re running the 3.3 release.

If this didn’t work, you will need to restore from the backup you made in step 1, and consider obtaining separate hardware to install MAAS 3.3.

How to upgrade a snap to MAAS 3.2

To upgrade from a earlier snap version to the 3.2 snap (using a region+rack configuration):

  1. Enter the following command:
sudo snap refresh --channel=3.2 maas
  1. Enter your account password.

The snap will refresh from the 3.2 channel; you will not need to re-initialise MAAS.

If you are using a multi-node maas deployment with separate regions and racks, you should first run the upgrade command above for rack nodes, then for region nodes.

How to upgrade MAAS 2.9++ to MAAS 3.2

To upgrade from MAAS 2.9 - 3.1 to MAAS 3.2, follow these steps:

  1. Back up your MAAS server completely; the tools and media are left entirely to your discretion.

  2. Add the MAAS 3.2 PPA to your repository list with the following command, ignoring any apparent error messages:

sudo apt-add-repository ppa:maas/3.2
  1. Run the MAAS upgrade:
sudo apt update
sudo apt upgrade maas

  1. Check your running MAAS install (by looking at the information on the bottom of the machine list) to make sure you’re running the 3.2 release.

  2. If this didn’t work, you will need to restore from the backup you made in step 1, and consider obtaining separate hardware to install MAAS 3.2.

How to upgrade MAAS 2.8-- to MAAS 3.2

If you are running MAAS 2.8 or lower, you can’t upgrade directly to MAAS 3.2:

  1. Make sure that the target system is running Ubuntu 20.04 LTS or higher:
lsb_release -a

The response should look something like this:

Distributor ID:	Ubuntu
Description:	Ubuntu xx.yy
Release:	xx.yy
Codename:	$RELEASE_NAME

The minimum “xx.yy” required for MAAS 3.2 is “20.04,” code-named “focal.”

  1. If you’re not running focal, upgrade the release:
sudo do-release-upgrade --allow-third-party

  1. Accept the defaults for any questions asked by the upgrade script.

  2. Reboot the machine when requested.

  3. Check whether the upgrade was successful:

lsb_release -a

A successful upgrade should respond with output similar to the following:

Distributor ID:	Ubuntu
Description:	Ubuntu 20.04(.nn) LTS
Release:	20.04
Codename:	focal

How to upgrade a snap to MAAS 3.1

To upgrade from a earlier snap version to the 3.1 snap (using a region+rack configuration):

  1. Refresh the snap:
sudo snap refresh --channel=3.1 maas
  1. Enter your account password.

The snap will refresh from the 3.1 channel. You will not need to re-initialise MAAS.

If you are using a multi-node maas deployment with separate regions and racks, you should first run the upgrade command above for rack nodes, then for region nodes.

How to upgrade MAAS 2.9++ to MAAS 3.1

You can upgrade from MAAS 2.9 or MAAS 3.0 to MAAS 3.1:

  1. Back up your MAAS server completely; the tools and media are left entirely to your discretion. Just be sure that you can definitely restore your previous configuration, should this procedure fail to work correctly.

  2. Add the MAAS 3.1 PPA to your repository list with the following command, ignoring any apparent error messages:

sudo apt-add-repository ppa:maas/3.1
  1. Run the MAAS upgrade like this:
sudo apt update
sudo apt upgrade maas

  1. Check your running MAAS install (by looking at the information on the bottom of the machine list) to make sure you’re running the 3.1 release.

  2. If this didn’t work, you will need to restore from the backup you made in step 1, and consider obtaining separate hardware to install MAAS 3.1.

How to upgrade MAAS 2.8-- to MAAS 3.1

If you are running MAAS 2.8 or lower, you can also upgrade directly to MAAS 3.1, but it requires some extra steps. You must first make sure that the target system is running Ubuntu 20.04 LTS or higher, by executing the following command:

lsb_release -a

The response should look something like this:

Distributor ID:	Ubuntu
Description:	Ubuntu xx.yy
Release:	xx.yy
Codename:	$RELEASE_NAME

The minimum “xx.yy” required for MAAS 3.0 is “20.04,” code-named “focal.”

If you are currently running Ubuntu bionic 18.04 LTS, you can upgrade to focal 20.04 LTS with the following procedure:

  1. Upgrade the release:
sudo do-release-upgrade --allow-third-party

  1. Accept the defaults for any questions asked by the upgrade script.

  2. Reboot the machine when requested.

  3. Check whether the upgrade was successful:

lsb_release -a

A successful upgrade should respond with output similar to the following:

Distributor ID:	Ubuntu
Description:	Ubuntu 20.04(.nn) LTS
Release:	20.04
Codename:	focal

How to upgrade a snap to MAAS 3.0

To upgrade from a earlier snap version to the 3.0 snap (using a region+rack configuration), do the following:

  1. Refresh the snap:
sudo snap refresh --channel=3.0 maas
  1. Enter your user password.

The snap will refresh from the 3.0 channel. You will not need to re-initialise MAAS.

If you are using a multi-node maas deployment with separate regions and racks, you should first run the upgrade command above for rack nodes, then for region nodes.

How to upgrade MAAS 2.9 to MAAS 3.0

To upgrade a working MAAS 2.9 instance to MAAS 3.0, follow these steps:

  1. Back up your MAAS server completely; the tools and media are left entirely to your discretion.

  2. Add the MAAS 3.0 PPA to your repository list:

sudo apt-add-repository ppa:maas/3.0
  1. Run the MAAS upgrade:
sudo apt update
sudo apt upgrade maas

  1. Check your running MAAS install (by looking at the information on the bottom of the machine list) to make sure you’re running the 3.0 release.

  2. If this didn’t work, you will need to restore from the backup you made in step 1, and consider obtaining separate hardware to install MAAS 3.0.

How to upgrade MAAS 2.8-- to MAAS 3.0

If you are running MAAS 2.8, you can upgrade directly to MAAS 3.0 with the following procedure:

  1. Check your release:
lsb_release -a

The response should look something like this:

Distributor ID:	Ubuntu
Description:	Ubuntu xx.yy
Release:	xx.yy
Codename:	$RELEASE_NAME

The minimum “xx.yy” required for MAAS 3.0 is “20.04,” code-named “focal.”

If you are currently running Ubuntu bionic 18.04 LTS, you can upgrade to focal 20.04 LTS with the following procedure:

  1. Upgrade the release:
sudo do-release-upgrade --allow-third-party

  1. Accept the defaults for any questions asked by the upgrade script.

  2. Reboot the machine when requested.

  3. Check whether the upgrade was successful:

lsb_release -a

A successful upgrade should respond with output similar to the following:

Distributor ID:	Ubuntu
Description:	Ubuntu 20.04(.nn) LTS
Release:	20.04
Codename:	focal

How to upgrade a snap to MAAS 2.9

To upgrade from an earlier snap version to the 2.9 snap (using a region+rack configuration), do the following:

  1. Refresh the snap:
sudo snap refresh --channel=3.0/stable maas
  1. Enter your user password.

The snap will refresh from the 3.0 channel. You will not need to re-initialise MAAS.

If you are using a multi-node maas deployment with separate regions and racks, you should first run the upgrade command above for rack nodes, then for region nodes.

How to upgrade MAAS 2.8-- to MAAS 2.9

MAAS 2.8 is the last supported version for Ubuntu 18.04 LTS. Newer versions of MAAS will not be back-portable, and consequently, to upgrade to MAAS 2.9 and all future versions, you will also need to upgrade the base operating system to Ubuntu 20.04.

You do these two operations all at once, with the following procedure:

  1. Add the 2.9 PPA to your repository path list:
sudo add-apt-repository ppa:maas/2.9
  1. Run the release upgrade:
sudo do-release-upgrade --allow-third-party

  1. Reboot your machine (requested by the upgrade script).

  2. Check that your upgrade was successful:

lsb_release -a

If the upgrade was successful, this command should yield output similar to the following:

No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.1 LTS
Release:	20.04
Codename:	focal

You have now upgraded to the Ubuntu 20.04 LTS base, and if you check your running MAAS install, you should see that the version has been updated to the latest stable 2.9 release.

Some installation notes

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.

How to get started with MAAS
MAAS documentation
MAAS Documentation
How-to guides
#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?