[FFE] New upstream release MAAS 2.1

Bug #1629909 reported by Andres Rodriguez on 2016-10-03
This bug affects 1 person
Affects Status Importance Assigned to Milestone
maas (Ubuntu)

Bug Description

Dependencies & Upgrade

MAAS users that are upgrading to Yakkety and 2.1, they will be able to continue to use MAAS exactly the same way how they were using it before, right after the upgrade without any user intervention. While MAAS 2.1 adds significant changes, it however, is currently provides full feature parity with any earlier version of MAAS.

MAAS introduces several new features/changes:

 - Support new consolidated images (squashfs)
 - Support for new HWE kernels & Low Latency kernels.
 - Support for NTP configuration
 - Support for third party and derived repositories.
 - Support for IPv6
 - Support for static routes
 - Support for Network Bridge Configuration
 - Introduce the First User Journey
 - Introduce Device Discovery

NOTE: Even with the newly introduced features, MAAS 2.1 is currently feature parity with older MAAS releases. This means that users will continue to use MAAS the same way they used to do it in previous releases, and current users upgrading wont be broken. The new features being introduced only enhance functionality.


 - We perform new install package testing to ensure that the package is rock solid on fresh installations.
 - We perform upgrade testing from previous MAAS and Ubuntu Releases. At the moment we perform upgrade testing covering upgrades from MAAS 2.0. The upgrade ensures that MAAS after the upgrade is up and running with no issues.


MAAS 2.1 is targeted to be released by Thursday October 13th and the goal is to perform a 0-day SRU for the final release.

NOTE: The only reason why MAAS 2.0 is being released as beta, is due to the introduction of the support for the new kernels that had been delayed due to reasons outside of MAAS control. As of beta1 all feature work is complete and we are only working on bug fixes moving forward.

Changed in maas (Ubuntu):
importance: Undecided → Critical
description: updated
description: updated
Steve Langasek (vorlon) wrote :

This is a large upstream change landing very late in the cycle, which is not ideal in terms of risk. I've reviewed the FFe request, and:
 - it addresses compatibility with the current kernels that we are releasing with in 16.10, which is pretty fundamental.
 - it contains some packaging changes, whose impact I have reviewed (some new dependencies added, but all of these are already in the server ISO with the exception of avahi-utils, which at 24k is trivially small).
 - this release has undergone install, upgrade, and workload testing upstream prior to upload.

Granting the FFe, with the understanding that there is no second chance to get this right on the release ISO if this version is broken.

Changed in maas (Ubuntu):
status: New → Triaged
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package maas - 2.1.0~beta2+bzr5454-0ubuntu1

maas (2.1.0~beta2+bzr5454-0ubuntu1) yakkety; urgency=medium

  * MAAS new upstream bugfix release. MAAS 2.1.0b2-bzr5454 (FFe LP: #1629909):
    - [2.1] Bootloaders not downloaded on initial import (LP: #1630394)
    - Cryptic error when PXE-boot requires an image not yet imported (LP: #1611949)
    - [2.0, 2.1, UI] MAAS webui allows boot disk to be changed on an
      already deployed node (LP: #1625676)
    - [2.1] Rename "Networks" tab to "Subnets" (LP: #1630591)
    - [2.1] netaddr assumes MAC OUI is ascii (LP: #1628761)
    - [2.1, 2.0] Can't input dynamic range on "Enable DHCP" after I deleted
      the dynamic range (LP: #1619262)
    - Machine unable to pxe with no-such-image while non-related images are
      being imported (LP: #1612203)
    - External DHCP detection is broken for a variety of reasons (LP: #1628645)
    - [2.1] expected string or bytes-like object (LP: #1627362)
    - [2.1] When trying to release a node, it gets stuck in releasing if
      there is no rack controller to power control (LP: #1614659)
    - WebUI needs a filter for deployed OS (LP: #1445941)

maas (2.1.0~beta1+bzr5433-0ubuntu1) yakkety; urgency=medium

  * MAAS new upstream release. MAAS 2.1.0b1-bzr5433 (FFe LP: #1629909):
    - Support for new version of streams.
    - Bootloaders are now downloaded from the streams.
    - Support for Low Latency kernels.
    - Support for new hardware enablement kernels.
    - Device discovery
      - UI ability to Map a network as an action.
      - Ability to select interval of active discovery.
      - Ability to enable active discovery per subnet.
  * Remove old template files on package removal.

 -- Andres Rodriguez <email address hidden> Wed, 05 Oct 2016 10:59:45 -0400

Changed in maas (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers