Reference: Release notes

Errors or typos? Topics missing? Hard to read? Let us know.

MAAS 3.4 provides several new features.

Redesigned UI

The MAAS User Interface (UI) has undergone a significant redesign, introducing the MAAS UI new layout. This new layout incorporates various features and improvements aimed at enhancing the user experience for MAAS users and operators who primarily interact with the UI. The MAAS UI new layout introduces several enhancements that aim to improve usability, customisation, and navigation within the application

  • Customised column visibility: One of the major improvements in the MAAS UI new layout is the ability for users to customize the visibility of columns on the machine list. This feature empowers users to focus on the specific information they need, while hiding irrelevant columns. By allowing users to tailor their view, this enhancement improves readability, reduces clutter, and provides a more personalised experience.

  • Action forms in side panel: Previously, the action forms in MAAS were located in the header section, which made it less intuitive for users to access and interact with them. The redesigned UI moves these action forms to the side panel, providing a more logical placement and easy access to perform actions on machines. This change enhances the usability of the forms and improves the overall workflow for users.

  • Streamlined action button group: The introduction of a new action button group eliminates the need for the previous “Take action” menu. Users can now directly access commonly used actions for machines, both in the details view and the machine list. This streamlines the workflow and simplifies the process of performing actions on machines, saving users time and effort.

  • Improved side navigation: To enhance navigation within the application, the MAAS UI new layout implements a new side navigation system. Users can conveniently navigate through different sections of the app using the side panel. Additionally, the inclusion of a secondary side navigation specifically for settings and account pages improves the organisation and accessibility of these sections.

Intended Benefits

The MAAS UI was redesigned with several user benefits in mind.

  • Enhanced table interaction: Users can now customize their views by selecting the columns they care about the most. This modular table feature allows for a personalised experience, ensuring users can focus on the information that matters to them.

  • Improved form interaction: Forms in the MAAS UI have been redesigned to scale with the content. By migrating all forms into panels, users have more space to view other components such as the machine list, resulting in a more comfortable and efficient form interaction experience.

  • Efficient navigation: The new layout addresses the challenges posed by a growing navigation menu. With the introduction of the side panel navigation, users can easily explore different sections of the app, providing a scalable and user-friendly navigation experience.

  • Enhanced search capability: The MAAS UI new layout improves the efficiency of the search feature. Users can search for machines based on conventions and tags, making it easier to find specific machines and take actions. The new layout also provides clearer feedback when the “take action” button is disabled, enhancing the overall search and interaction experience.

  • Performance improvements based on user feedback: Based on user feedback received through Discourse, several performance issues have been identified and addressed. The MAAS team has worked diligently to optimise machine information loading times and resolve delays encountered while opening machine pages. These performance improvements ensure a smoother and faster user experience when interacting with the MAAS UI.

The MAAS UI new layout introduces a redesigned interface with enhanced features to provide a more efficient and user-friendly experience for MAAS users and operators. By allowing users to customize their views, streamlining form interactions

Configurable session timeout

In MAAS 3.4, we’ve introduced the Configurable Session Timeout feature, offering better control over session length. This feature allows you to set a personalised duration for your sessions, hopefully avoiding abrupt disconnections or lingering sessions. If you’re a user who has login repeatedly, due to short session defaults, or you’re concerned about leaving your session accessible for too long, setting a custom timeout is useful and potentially more secure.

Packer MAAS - SLES

The MAAS 3.4 release expands Packer support to include SUSE Linux Enterprise Server (SLES), expanding the the list of deployable Linux distributions. We also support openSUSE and openSUSE Tumbleweed. And we’ve added a template for Red Hat Enterprise Linux (RHEL) version 9.

Install MAAS (3.4)

MAAS will run on just about any modern hardware configuration.

Bug fixes (3.4)

Here is the list of bug fixes for all versions of MAAS 3.4, from first Beta through final release:

  • (3.4.0)2038381^: Hardware Sync Docs link in UI leads to a 404
  • (3.4.0)2045228^: DNS updates are consumed concurrently, leading to an incorrect nsupdate payload
  • (3.4.0)1908452^: MAAS stops working and deployment fails after Loading ephemeral step
  • (3.4.0)2022082^: 30-maas-01-bmc-config commissioning script fails on Power9 (ppc64le)
  • (3.4-rc1)2003745^: Cannot deploy older Ubuntu releases
  • (3.4-rc1)2026802^: MAAS 3.4 installed with deb fails to start the rack due to permission error
  • (3.4-rc1)2027735^: Concurrent API calls don’t get balanced between regiond processes
  • (3.4-rc1)2029481^: MAAS 3.4 RC (Aug 2nd 2023) breaks DNS
  • (3.4-rc1)2003812^: MAAS servers have two NTP clients
  • (3.4-rc1)2023138^: UI: Deleted machines don’t correctly update MAAS web UI
  • (3.4-rc1)2022926^: Wrong metadata url in enlist cloud-config
  • (3.4-rc1)2012801^: MAAS rDNS returns two hostnames that lead to Services not running that should be: apache2, SSLCertificateFile: file '/etc/apache2/ssl//cert_ does not exist or is empty
  • (3.4-rc1)2025375^: Machine listing pagination displays incorrect total number of pages
  • (3.4-rc1)2027621^: ipv6 addresses in dhcpd.conf
  • (3.4-rc1)1914812^: curtin fails to deploy centos 8 on nvme with multipath from ubuntu 20.04
  • (3.4-rc1)2020397^: Custom images which worked ok is not working with 3.2
  • (3.4-rc1)2024625^: DNS Forward failures
  • (3.4-rc1)1880016^: show image last synced time
  • (3.4-rc1)2023207^: MAAS Images show “last deployed” as null even after being deployed
  • (3.4-rc1)2025468^: maas-dhcp-helper stopped working which gives issues with DNS updates
  • (3.4-rc1)1995053^: maas config-tls requires root but WebUI instruction assumes a normal user
  • (3.4-rc1)2018310^: MAAS UI warns about PostgreSQL version but link does not help
  • (3.4-beta3)2020882^: Machine config hints FileNotFoundError
  • (3.4-beta3)2022833^: machine-config-hints fails on Power machines
  • (3.4-beta3)1835153^: Ephemeral deployment creates pending ScriptResult
  • (3.4-beta3)1996204^: failing metrics cause 500 error
  • (3.4-beta3)2011841^: DNS resolution fails
  • (3.4-beta3)2013529^: Nodes stuck in Failed Disk Erasing due to wrong ipxe boot file
  • (3.4-beta3)2021965^: MAAS Settings (sidebar) scroll issue
  • (3.4-beta3)1807725^: Machine interfaces allow ‘_’ character, results on a interface based domain breaking bind (as it doesn’t allow it for the host part).
  • (3.4-beta3)2006497^: unsupported configuration in virsh command
  • (3.4-beta3)2011853^: Auto-discovered subnet does not get correct VLAN
  • (3.4-beta3)2020865^: flaky test: src/tests/maasperf/cli/ 1974050^: Vmware no longer supports image cloning
  • (3.4-beta2)2009209^: snap deployed maas is not able to use openstack nova power type due to missing python3-novaclient dependency
  • (3.4-beta2)1830619^: The “authoritative” field value is ignored when creating/editing domains
  • (3.4-beta2)1914762^: test network configuration broken with openvswitch bridge
  • (3.4-beta2)1999668^: reverse DNS not working for some interfaces
  • (3.4-beta2)2016908^: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
  • (3.4-beta2)2019229^: 3.4.0~beta1 maas-region-api fails to start with pylxd 2.3.2~alpha1-420-10-g.72426bf~ubuntu22.04.1
  • (3.4-beta2)1818672^: Option to show full name of a user in the UI
  • (3.4-beta2)1823153^: maas init doesn’t check if the user or email already exists
  • (3.4-beta2)1876365^: host passthrough not working with KVMs
  • (3.4-beta2)2018149^: MAAS generates netplan with illegal autoconf and accept_ra flags for 22.04
  • (3.4-beta2)2020427^: crash importing large database dump into maas-test-db
  • (3.4-beta1)1999160^: Region controller fails to run commissioning scripts in proxied environment
  • (3.4-beta1)1999191^: bad interaction between Colorama and the CLI
  • (3.4-beta1)1999557^: MAAS fails to startup when installed from deb package and vault is enabled
  • (3.4-beta1)2002109^: Migration of BMC power credentials fails with manual driver
  • (3.4-beta1)2002111^: Connection to local Vault fails if proxy is configured
  • (3.4-beta1)2003888^: Grouped machine list view: Inconsistent display when machine state changes
  • (3.4-beta1)1743648^: Image import fails
  • (3.4-beta1)1811799^: Normal users can read machine details of owned machines
  • (3.4-beta1)1812377^: An admin is allowed to create raids for an Allocated node in the UI, but not the API
  • (3.4-beta1)1958451^: power_driver parameter is not preserved
  • (3.4-beta1)1990172^: “20-maas-03-machine-resources” commissioning script improperly reports a Pass when the test fails
  • (3.4-beta1)1995084^: MAAS TLS sets HSTS forcibly and with too short value
  • (3.4-beta1)1999147^: [3.3.0-candidate] failure when arch is requested as a filter
  • (3.4-beta1)1999368^: [3.3.0 RC] wrong DNS records
  • (3.4-beta1)1999579^: MAAS OpenAPI docs are not available in air-gapped mode
  • (3.4-beta1)2001546^: Server reboot will make subnet entries disappear from zone.maas-internal
  • (3.4-beta1)2003310^: Refresh scripts are not re-run if they pass, but fail to report the results to the region
  • (3.4-beta1)2003940^: MAAS 3.3 RC shows incorrect storage amount
  • (3.4-beta1)2008275^: Intel AMT support is broken in MAAS 3.3.0
  • (3.4-beta1)2009137^: MAAS OpenApi Schema missing parameters
  • (3.4-beta1)2009186^: CLI results in connection timed out when behind haproxy and 5240 is blocked
  • (3.4-beta1)2009805^: machine deploy install_kvm=True fails
  • (3.4-beta1)2011274^: MAAS 3.4: Deployment fails on LXD VMs
  • (3.4-beta1)2011822^: Reverse DNS resolution fails for some machines
  • (3.4-beta1)2012139^: maas commands occasionally fail with NO_CERTIFICATE_OR_CRL_FOUND when TLS is enabled
  • (3.4-beta1)2017504^: Cannot deploy from the cli when “Allow DNS resolution” is set on minimal subnet
  • (3.4-beta1)1696108^: Interface model validates the MAC address twice
  • (3.4-beta1)1773150^: smartctl verify fails due to Unicode in Disk Vendor Name
  • (3.4-beta1)1773671^: MAC address column should use mono font
  • (3.4-beta1)1959648^: Websocket vlan handler should include associated subnet ids
  • (3.4-beta1)1979403^: commission failed with MAAS 3.1 when BMC has multiple channels but the first channel is disabled
  • (3.4-beta1)1986590^: maas-cli from PPA errors out with traceback - (3.4-beta1)ModuleNotFoundError: No module named ‘provisioningserver’
  • (3.4-beta1)1990416^: MAAS reports invalid command to run when maas-url is incorrect
  • (3.4-beta1)1993618^: Web UI redirection policy can invalidate HAProxy and/or TLS setup
  • (3.4-beta1)1994945^: Failure to create ephemeral VM when no architectures are found on the VM host
  • (3.4-beta1)1996997^: LXD resources fails on a Raspberry Pi with no Ethernet
  • (3.4-beta1)1999064^: does not clean up temporary directory
  • (3.4-beta1)2002550^: Controller type displays as “Undefined”
  • (3.4-beta1)2007297^: LXD REST API connection goes via proxy
  • (3.4-beta1)2009045^: WebSocket API to report reasons for failure for machine bulk actions
  • (3.4-beta1)2009140^: MAAS OpenApi Schema cutoff variable names
  • (3.4-beta1)2012054^: RPC logging when debug is too verbose

Cloud-init bug 1910552 was also fixed during the MAAS 3.4-Beta1 cycle and incorporated into that release.


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

Thanks for this doc! Some feedback from someone walking through it:

  • While there’s a clear deprecation warning at the top for v12, there’s implicitly conflicting info later on about which version of PostgreSQL is required. In “Setting up PostgreSQL from scratch”, it says “version 10 or better”. When listing which pg_hba.conf to edit, it hardcodes the directory for version 14. In “How to initialise MAAS 3.3 snap”, it has a prompt from version 12 (psql (12.4)). For someone who skips “right to” the how to install portion, it might be good to make these consistent, and maybe even remind the reader that they need to be using v14 in this section as well.
  • Nit: -y is an unnecessary argument to sudo apt update
  • While it says to run MAAS 3.3 packages on 22.04 LTS only, there’s no advice about which host OS release to use for the snap. While snaps generally are more platform independent, postgres 14 is not available in focal, so it would be good IMO to point that out before getting too far.

good calls, all. lemee see what i can do here. :slight_smile: