We are pleased to announce that MAAS 3.6 has been released with new features and many bug fixes. Check it out!
1 Like
Nice work!
I’ve attempted to upgrade my MAAS 3.5 on Ubuntu 22.04 to 3.6 on 24.04, however the upgrade to 24.04 uninstalled MAAS and reinstalling it after the upgrade yields:
Setting up python3-django-maas (1:3.6.0-17541-g.561fe1a3ec-0ubuntu1~24.04.1) ...
Setting up tcpdump (4.99.4-3ubuntu4) ...
Setting up freeipmi-tools (1.6.13-3) ...
Setting up maas-rack-controller (1:3.6.0-17541-g.561fe1a3ec-0ubuntu1~24.04.1) ...
...
File "/usr/lib/python3/dist-packages/piston3/utils.py", line 15, in <module>
from django.utils.translation import ugettext as _
ImportError: cannot import name 'ugettext' from 'django.utils.translation' (/usr/lib/python3/dist-packages/django/utils/translation/__init__.py). Did you mean: 'gettext'?
I’m not sure if I’ve made a mistake or if I should submit a ticket to the bug tracker.
(In any case I always make a backup before dist-upgrading so for now I’ve rolled back to 22.04/3.5)
Try on a clean 24.04 to see if the error reproduces. You went from 3.5 on 22.04 to 3.6 on 24.04, so the OS got upgraded with MAAS 3.5 on the system, which might have held back some packages. Let us know if that works or if any bugs persist, and then we can decide if we need to file one.
Does not reproduce on a fresh 24.04 install with MAAS 3.6, so that is good.
I am running MAAS 3.5.4 on Ubuntu 22.04 from package, not snap . Would like to upgrade to 3.6, but it looks like its only for 24.04.
How can I perform the upgrade without losing the existing configuration?
You first have to upgrade to ubuntu 24.04 and postgres16, and then you upgrade MAAS. The upgrade scenario is of course covered, but I suggest to take a backup just in case.
It seems that upgrade to 24.04 removes MAAS from the system.
That’s weird. Did you sudo do-release-upgrade --allow-third-party?
https://maas.io/docs/how-to-install-maas#p-9034-upgrade-package-ppa-based-installations
No, just the regular do-release-upgrade.
Will try yhat with the switch, thanks!
Performed the upgrade, now maas-temporal.service is not starting.
The error is:
sql schema version compatibility check failed: pq: password authentication failed for user "maas"
Reverted to pre-OS upgrade snapshot.
did you upgrade postgres as well? can you login to postgres with the maas user’s credentials?
No, thhe postgres is still on v14, but I am not usinng the default DB credentials.
is postgres up and running after the upgrade? Can you ensure that you can connect using the credentials in /etc/maas/regiond.conf?
How do I perform such connectivity test?
sudo -u postgres PGPASSWORD=<password> psql --username=<username> -d <database> -h 127.0.0.1
replace the strings with the ones you extract from /etc/maas/regiond.conf
In pre-upgradeed system it works.
Will perform the upgrade and will try again.
I’ve tried a clean install of MAAS but when I run the init for region+rack; the server seems to fail to start rackd (frontend + region controller seems to work fine, but it doesn’t identify as a rack controller):
May 07 15:02:48 maas.pebble[295730]: 2025-05-07T15:02:48.221Z [pebble] Service "rackd" starting: sh -c "exec systemd-cat -t maas-rackd $SNAP/bin/run-rackd"
May 07 15:02:48 maas-rackd[295877]: Can't locate Config.pm in @INC (you may need to install the Config module) (@INC entries checked: /etc/perl /usr/local/lib/aarch64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 /usr/lib/aarch64-linux-gnu/perl5/5.38 /usr/share/perl5 /usr/lib/aarch64-linux-gnu/perl-base /usr/lib/aarch64-linux-gnu/perl/5.38 /usr/share/perl/5.38 /usr/local/lib/site_perl).
May 07 15:02:48 maas-rackd[295877]: BEGIN failed--compilation aborted.
May 07 15:02:48 maas.pebble[295730]: 2025-05-07T15:02:48.323Z [pebble] Change 1 task (Start service "rackd") failed: cannot start service: exited quickly with code 2
Any ideas what’s going on with perl here?
For information I’m running on 24.04 Ubuntu LTS and installing via snap
Reinstalling MAAS 3.5 initializes region+rack just fine (doing an upgrade to 3.6 breaks rackd)
1 Like
Thanks for the information, that was super helpful 
@r00ta , thank you very much, the upgrade worked.