| 2018-05-24 15:36:17 |
Andres Rodriguez |
bug |
|
|
added bug |
| 2018-05-24 15:40:53 |
Andres Rodriguez |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-05-24 15:40:53 |
Andres Rodriguez |
bug task added |
|
maas (Ubuntu Bionic) |
|
| 2018-05-24 15:40:53 |
Andres Rodriguez |
nominated for series |
|
Ubuntu Cosmic |
|
| 2018-05-24 15:40:53 |
Andres Rodriguez |
bug task added |
|
maas (Ubuntu Cosmic) |
|
| 2018-05-24 15:41:10 |
Andres Rodriguez |
bug task deleted |
maas (Ubuntu Cosmic) |
|
|
| 2018-05-24 15:47:05 |
Andres Rodriguez |
description |
[Description]
We would like to request a SRU for MAAS 2.4. This follows the draft SRU exception process described at https://wiki.ubuntu.com/MAASUpdates
[Impact]
This is the final release of MAAS 2.4, aka 2.4.0. This release fixes all the issues found in the MAAS 2.4.0~beta2 release currently in bionic that were found during automated and manual testing.
[Regression Potential]
Minimal. 2.4.0 fixes all those issues and blockers found on 2.4b2. This includes stability, robustness, API and UI issues.
Tests done:
1. MAAS CI Lab:
- Tests Installation (from pkgs), configuration / customization of MAAS, enlistment, commissioning. It also tests deployments with Juju.
- Tests various API's
- Tests are performed against Bionic
2. Other manual testing include:
- Installation (both fresh and upgrades)
- Configuration
- Taking nodes through the lifecycle for regression testing.
- Custom configuration to ensure proper operation.
3. Solutions QA testing
- The solutions QA tests MAAS against all other Canonical provides, and releases are vetted by them. This confirms that all integration tests against their environment and all other canonical products (Juju deploying OpenStack, k8s) work without any regressions, or without encountering the issues found in 2.4b2. |
[Impact]
This is the new and final release of MAAS 2.4.0. This release includes various bugfixes since MAAS 2.4b2.
[Test Case]
MAAS Testing
------------
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.
Solutions QA
------------
MAAS releases are also now vetted by the Solutions QA team. The test they run ensure there are no regression for their use cases. This release has been accepted / vetted by them.
[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.
The Solutions QA team tests MAAS against various version of Juju to deploy Openstack and has vetted this release and confirmed all issues present on 2.4b2 are no longer present. |
|
| 2018-05-24 17:06:16 |
Andres Rodriguez |
bug |
|
|
added subscriber Ubuntu SRU developers |
| 2018-05-24 20:15:31 |
Andres Rodriguez |
maas (Ubuntu): status |
New |
Fix Released |
|
| 2018-05-24 20:15:41 |
Andres Rodriguez |
nominated for series |
|
Ubuntu Cosmic |
|
| 2018-05-24 20:15:41 |
Andres Rodriguez |
bug task added |
|
maas (Ubuntu Cosmic) |
|
| 2018-05-25 00:57:42 |
Yoshi Kadokawa |
bug |
|
|
added subscriber Yoshi Kadokawa |
| 2018-05-30 00:13:17 |
Chris Halse Rogers |
maas (Ubuntu Bionic): status |
New |
Incomplete |
|
| 2018-05-30 17:09:29 |
Andres Rodriguez |
maas (Ubuntu Bionic): status |
Incomplete |
New |
|
| 2018-07-28 04:49:12 |
Steve Langasek |
maas (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2018-07-28 04:49:14 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-07-28 04:49:16 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2018-07-28 04:49:19 |
Steve Langasek |
tags |
|
verification-needed verification-needed-bionic |
|
| 2018-08-02 13:57:20 |
Andres Rodriguez |
tags |
verification-needed verification-needed-bionic |
verification-done verification-done-bionic |
|
| 2018-08-06 22:23:29 |
Brian Murray |
bug |
|
|
added subscriber Brian Murray |
| 2018-08-15 14:10:02 |
Andres Rodriguez |
summary |
[SRU] MAAS 2.4.0 |
[SRU] MAAS 2.4.1 |
|
| 2018-08-15 14:12:30 |
Andres Rodriguez |
description |
[Impact]
This is the new and final release of MAAS 2.4.0. This release includes various bugfixes since MAAS 2.4b2.
[Test Case]
MAAS Testing
------------
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.
Solutions QA
------------
MAAS releases are also now vetted by the Solutions QA team. The test they run ensure there are no regression for their use cases. This release has been accepted / vetted by them.
[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.
The Solutions QA team tests MAAS against various version of Juju to deploy Openstack and has vetted this release and confirmed all issues present on 2.4b2 are no longer present. |
[Impact]
Bionic currently has MAAS 2.4.0~beta2 in the main archive, which is a release which is known to not fully work. Currently users in Bionic are limited by the beta release, which 2.4.0 final and 2.4.1 now fix.
[Test Case]
MAAS Testing
------------
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.
Solutions QA
------------
MAAS releases are also now vetted by the Solutions QA team. The test they run ensure there are no regression for their use cases. This release has been accepted / vetted by them.
[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.
The Solutions QA team tests MAAS against various version of Juju to deploy Openstack and has vetted this release and confirmed all issues present on 2.4b2 are no longer present. |
|
| 2018-08-15 14:15:25 |
Andres Rodriguez |
description |
[Impact]
Bionic currently has MAAS 2.4.0~beta2 in the main archive, which is a release which is known to not fully work. Currently users in Bionic are limited by the beta release, which 2.4.0 final and 2.4.1 now fix.
[Test Case]
MAAS Testing
------------
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.
Solutions QA
------------
MAAS releases are also now vetted by the Solutions QA team. The test they run ensure there are no regression for their use cases. This release has been accepted / vetted by them.
[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.
The Solutions QA team tests MAAS against various version of Juju to deploy Openstack and has vetted this release and confirmed all issues present on 2.4b2 are no longer present. |
[Impact]
Bionic currently has MAAS 2.4.0~beta2 in the main archive, which is a release which is known to not fully work. Currently users in Bionic are limited by the beta release, which 2.4.0 final and 2.4.1 now fix.
2.4.0 has already been reviewed and is in -proposed. 2.4.1 includes bug fixes and completes the feature set for MAAS 2.4:
https://launchpad.net/maas/+milestone/2.4.1
[Test Case]
MAAS Testing
------------
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.
Solutions QA
------------
MAAS releases are also now vetted by the Solutions QA team. The test they run ensure there are no regression for their use cases. This release has been accepted / vetted by them.
[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.
The Solutions QA team tests MAAS against various version of Juju to deploy Openstack and has vetted this release and confirmed all issues present on 2.4b2 are no longer present. |
|
| 2018-08-15 22:34:08 |
Launchpad Janitor |
maas (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2018-08-15 22:34:16 |
Steve Langasek |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2018-08-16 19:44:41 |
Andres Rodriguez |
summary |
[SRU] MAAS 2.4.1 |
[SRU] MAAS 2.4.0 |
|
