← Back to team overview

maas-devel team mailing list archive

MAAS 1.9.0 beta 1 released.

 

I'm happy to announce that MAAS 1.9.0 Beta 1 has been released for testing.
Notable changes:

*Changes:*

   - *Custom LVM Configuration (WebUI)*
      - Users can now custom configure LVM in the MAAS Node Details WebUI.


   - *RAID Configuration (WebUI)*
      - Users can now configure RAID in the MAAS Node Details page. It
      currently supports RAID 0, 1, 5, 6.


   - *Bug Fixes:*
      -
      - LP: #1507359 - Juju says centos7, maas says centos70 (maas should
      say centos7)
      - LP: #1501982 - Network's filter doesn't show networks.
      - LP: #1510109 - Fail to deploy when creating custom LVM
      - LP: #1510121 - Fail to deploy when creating custom partition
      (sda-part1)
      - LP: #1497991 - failed pxe boot causes system to local boot old
      deployment - node gets marked deployed
      - LP: #1509405 - Interface_set missing from the node api
      - LP: #1508059 - Node interface configuration should only be allowed
      when the node is ready
      - LP: #1505030 - fabric autocreation per physical cluster interface
      (vlan autocreation as well)
      - LP: #1490711 - MAAS doesn't allow you to select HWE kernel during
      commissioning
      - LP: #1508695 - ip addr parser can assert and fail for some IPv6
      addresses
      - LP: #1499378 - Internal Server Error when bind not running
      - LP: #1505032 - Fabric class
      - LP: #1501613 - MAAS needs to reload page when region version changes
      - LP: #1484698 - If node is released while DHCP is down, IP address
      remains reserved
      - LP: #1499062 - Internal Server error when 'Sync URL' has a
      preceding whitespace or non-URL
      - LP: #1489529 - Internal Server error when Determining maas version
      for apt cache
      - LP: #1504268 - Rename fabric/spaces
      - LP: #1506909 - Node name cannot be changed due to unrelated error
      - LP: #1506991 - MAAS should tell cloud-init not to contact
      metadataserver on every boot
      - LP: #1503467 - Device shown on the node listing page
      - LP: #1504861 - Device action button in incorrect position
      - LP: #1381000 - UI doesn't warm about missing Power Management tools
      (+1505386)
      - LP: #1505029 - Cluster controller interface detection needs to
      avoid virbr0/lxcbr0/

*Known problems and Work Arounds (Recurring from Alpha2)*



   - *Fail to deploy (boot) with UEFI*

MAAS seems to successfully install a system that's configured with UEFI,
however, the node will fail to boot. There's no work around at the moment
other than changing the system from UEFI to Legacy boot. This has only been
tested in one set of systems.
*- https://launchpad.net/bugs/1510120 <https://launchpad.net/bugs/1510120>*


   - CentOS fails to deploy when deploying with LVM

MAAS will fail to deploy CentOS with LVM by default. This can be changed by
changing the Setting of the default deployment layout to Flat. This can be
done in the MAAS Settings page under the storage section.

*https://launchpad.net/bugs/1499558 <https://launchpad.net/bugs/1499558>*


*Testing*
MAAS 1.9.0 Beta 1 is available for testing in:

*ppa:maas/next*

Happy testing!
-- 
Andres Rodriguez
Engineering Manager, MAAS & OIL DevOps
Canonical USA, Inc.