Skip to main content
  1. Blog
  2. Article

Canonical
on 5 September 2017

MAAS Development Update – Aug 21st – Sept 1st


Hello MAASters! This is the development summary for the past couple of weeks:

MAAS 2.3 (current development release)

Hardware Testing Phase 2

  • Added parameters form for script parameters validation.
  • Accept and validate results from nodes.
  • Added hardware testing 7zip CPU benchmarking builtin script.
  • WIP – ability to send parameters to test scripts and process results of individual components. (e.g. will provide the ability for users to select which disk they want to test, and capture results accordingly)
  • WIP – disk benchmark test via Fio.

Network beaconing & better network discovery

  • MAAS controllers now send out beacon advertisements every 30 seconds, regardless of whether or not any solicitations were received.

Switch Support

  • Backend changes to automatically detect switches (during commissioning) and make use of the new switch model.
  • Introduce base infrastructure for NOS drivers, similar to the power management one.
  • Install the Rack Controller when deploying a supported Switch (Wedge 40, Wedge 100)
  • UI – Add a switch listing tab behind a feature flag.

Minor UI improvements

  • The version of MAAS installed on each controller is now reported on the controller details page.

python-libmaas

  • Added ability to power on, power off, and query the power state of a machine.
  • Added PowerState enum to make it easy to check the current power state of a machine.
  • Added ability to reference the children and parent interfaces of an interface.
  • Added ability to reference the owner of node.
  • Added base level `Node` object that `Machine`, `Device`, `RackController`, and `RegionController` extend from.
  • Added `as_machine`, `as_device`, `as_rack_controller`, and `as_region_controller` to the Node object. Allowing the ability to convert a `Node` into the type you need to perform an action on.

Bug fixes:

  • LP: #1676992 – force Postgresql restart on maas-region-controller installation.
  • LP: #1708512 – Fix DNS & Description misalignment
  • LP: #1711714 – Add cloud-init reporting for deployed Ubuntu Core systems
  • LP: #1684094 – Make context menu language consistent for IP ranges.
  • LP: #1686246 – Fix docstring for set-storage-layout operation
  • LP: #1681801 – Device discovery – Tooltip misspelled
  • LP: #1688066 – Add Spice graphical console to pod created VM’s
  • LP: #1711700 – Improve DNS reloading so its happens only when required.
  • LP: #1712423, #1712450, #1712422 – Properly handle a ScriptForm being sent an empty file.
  • LP: #1621175 – Generate password for BMC’s with non-spec compliant password policy
  • LP: #1711414 – Fix deleting a rack when it is installed via the snap
  • LP: #1702703 – Can’t run region controller without a rack controller installed.

This article originally appeared at Andres Rodriguez's blog

Related posts


Luci Stanescu
14 May 2026

Fragnesia Linux kernel local privilege escalation vulnerability mitigations

Ubuntu Article

A local privilege escalation (LPE) vulnerability affecting the Linux kernel has been publicly disclosed on May 13, 2026. The vulnerability does not have a CVE ID published, but is referred to as “Fragnesia.”  The vulnerability affects multiple Linux distributions, including all Ubuntu releases. The affected components are the Linux kernel ...


Bertrand Boisseau
13 May 2026

Rethinking BYOD security: protecting data without trusting devices

Ubuntu Article

BYOD (bring your own device) has always looked better on paper than it does in real life. The promise is clear: let people use the gadgets they already own. Less friction, lower costs, and more freedom. But when security and privacy are non-negotiable, the conversation around BYOD usually ends quickly. Not because BYOD is a ...


Luci Stanescu
8 May 2026

Dirty Frag Linux kernel local privilege escalation vulnerability mitigations

Ubuntu Article

Two local privilege escalation (LPE) vulnerabilities affecting the Linux kernel have been publicly disclosed on May 7, 2026. The vulnerabilities have been assigned the IDs CVE-2026-43284 and CVE-2026-43500 and are referred to as “Dirty Frag.” The affected components are Linux kernel modules. The first vulnerability impacts the modules tha ...