Ubuntu
maas package

[SRU] MAAS 2.2.0

Bug #1696752 reported by Andres Rodriguez
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
maas (Ubuntu)
Fix Released
High
Unassigned
Xenial
Fix Released
Undecided
Unassigned
Yakkety
Fix Released
Undecided
Unassigned
Zesty
Fix Released
Undecided
Unassigned

Bug Description

[Impact]
This is a new upstream release that addresses various issues present in 2.1 and introduces various features that improve the robustness, and feature set of MAAS.

MAAS 2.2.0 introduces the following features:

 * Intel Rack Scale Design support (via MAAS Pods).
 * Hardware Testing
 * DHCP Relay support
 * Unmanaged Subnets
 * L2 spaces
 * Improve Windows deployment support.
 * Facebook's wedge 40 & 100 discovery and deployment
 * Various UI & UX improvements
 * More robust commissioning environment

[Test Case]
MAAS testing has been done in various cases, partially documented https://wiki.ubuntu.com/MAASUpdates. This include:

1. Manual Fresh installation of MAAS
2. Manual upgrade from the previous Ubuntu Release.
3. Automated (CI) testing of MAAS install and operation as per the MAAS' CI.
4. Automated (CI) testing of MAAS install and operation against other Canonical's product (juju, Canonical OpenStack & Kubernetes) provided by the Canonical Solutions QA Team.
5. Manual split region/rack test are performed. This is to ensure that if we upgrade a MAAS Region to a newer version, the MAAS rack of the older version remains connected and operational.

All of this includes verifying normal operation, issues fixed, and ensuring that Canonical Cloud solutions can inter-operate. MAAS releases are also now vetted by the Solutions QA team.

[Regression Potential]
Minimal (For MAAS itself). MAAS is fully backwards compatible and handles upgrades from previous releases which result in the continuous operation of MAAS. Users will continue to use this new version of MAAS as they used it before.

Medium (For not tested set of hardware) - A new version of Curtin has been SRU'd, and as such, this could impact the deployment of untested hardware Paths. MAAS, in itself, has not changed the way it deploys machines, but curtin (the one in charge of network, disk & boot-order) has.

See original description
Andres Rodriguez (andreserl)
Changed in maas (Ubuntu):
importance: Undecided → High
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello Andres, or anyone else affected,

Accepted maas into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/maas/2.2.0+bzr6054-0ubuntu2~17.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty.If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in maas (Ubuntu Zesty):
status: New → Fix Committed
tags: added: verification-needed verification-needed-zesty
Andres Rodriguez (andreserl)
description: updated
Andres Rodriguez (andreserl)
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote :

With regards to the upgrade path, what testing is done around partial upgrades that leave a region and rack controller at different versions?

description: updated
Andres Rodriguez (andreserl)
description: updated
Andres Rodriguez (andreserl)
description: updated
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote :

Hello Andres, or anyone else affected,

Accepted maas into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/maas/2.2.0+bzr6054-0ubuntu2~16.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-yakkety to verification-done-yakkety. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-yakkety. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in maas (Ubuntu Yakkety):
status: New → Fix Committed
tags: added: verification-needed-yakkety
Changed in maas (Ubuntu Xenial):
status: New → Fix Committed
tags: added: verification-needed-xenial
Revision history for this message
Steve Langasek (vorlon) wrote :

Hello Andres, or anyone else affected,

Accepted maas into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/maas/2.2.0+bzr6054-0ubuntu2~16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Revision history for this message
Andres Rodriguez (andreserl) wrote :

I've verified -proposed on all releases and marked this as verification-done.

tags: added: verification-done verification-done-xenial verification-done-yakkety verification-done-zesty
removed: verification-needed verification-needed-xenial verification-needed-yakkety verification-needed-zesty
Revision history for this message
Andres Rodriguez (andreserl) wrote :

The versions in -proposed for all releases have been tested as per the description of the bug.

 2.2.0+bzr6054-0ubuntu2~17.04.1
 2.2.0+bzr6054-0ubuntu2~16.10.1
 2.2.0+bzr6054-0ubuntu2~16.04.1

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package maas - 2.2.0+bzr6054-0ubuntu2~17.04.1

---------------
maas (2.2.0+bzr6054-0ubuntu2~17.04.1) zesty-proposed; urgency=medium

  * Stable Release Update. New MAAS upstream release 2.2.0 (LP: #1696752)
    - Support for Intel Rack Scale Design as a MAAS Pod.
    - Support for KVM as a MAAS Pod.
    - Support for Hardware Testing.
    - Support for Unmanaged Subnets.
    - Support for L2 Spaces.
    - Support for DHCP Relay.
    - Support for FB Wedge 40 & 100 switch discovery and deployment.
    - Improve Windows deployment.
    - Improved Commissioning environment.
    - Improved UX & UI.

 -- Andres Rodriguez <email address hidden> Thu, 08 Jun 2017 19:42:04 -0400

Changed in maas (Ubuntu Zesty):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for maas has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package maas - 2.2.0+bzr6054-0ubuntu2~16.10.1

---------------
maas (2.2.0+bzr6054-0ubuntu2~16.10.1) yakkety-proposed; urgency=medium

  * Stable Release Update. New MAAS upstream release 2.2.0 (LP: #1696752)
    - Support for Intel Rack Scale Design as a MAAS Pod.
    - Support for KVM as a MAAS Pod.
    - Support for Hardware Testing.
    - Support for Unmanaged Subnets.
    - Support for L2 Spaces.
    - Support for DHCP Relay.
    - Support for FB Wedge 40 & 100 switch discovery and deployment.
    - Improve Windows deployment.
    - Improved Commissioning environment.
    - Improved UX & UI.

 -- Andres Rodriguez <email address hidden> Thu, 08 Jun 2017 19:42:04 -0400

Changed in maas (Ubuntu Yakkety):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package maas - 2.2.0+bzr6054-0ubuntu2~16.04.1

---------------
maas (2.2.0+bzr6054-0ubuntu2~16.04.1) xenial-proposed; urgency=medium

  * Stable Release Update. New MAAS upstream release 2.2.0 (LP: #1696752)
    - Support for Intel Rack Scale Design as a MAAS Pod.
    - Support for KVM as a MAAS Pod.
    - Support for Hardware Testing.
    - Support for Unmanaged Subnets.
    - Support for L2 Spaces.
    - Support for DHCP Relay.
    - Support for FB Wedge 40 & 100 switch discovery and deployment.
    - Improve Windows deployment.
    - Improved Commissioning environment.
    - Improved UX & UI.

 -- Andres Rodriguez <email address hidden> Thu, 08 Jun 2017 19:42:04 -0400

Changed in maas (Ubuntu Xenial):
status: Fix Committed → Fix Released
Andres Rodriguez (andreserl)
Changed in maas (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.