Activity log for bug #1708651

Date Who What changed Old value New value Message
2017-08-04 12:31:25 Andres Rodriguez bug added bug
2017-08-04 12:31:41 Andres Rodriguez nominated for series Ubuntu Zesty
2017-08-04 12:31:41 Andres Rodriguez bug task added maas (Ubuntu Zesty)
2017-08-04 12:31:41 Andres Rodriguez nominated for series Ubuntu Xenial
2017-08-04 12:31:41 Andres Rodriguez bug task added maas (Ubuntu Xenial)
2017-08-04 12:54:56 Andres Rodriguez bug added subscriber Ubuntu Stable Release Updates Team
2017-08-04 15:03:25 Andres Rodriguez maas (Ubuntu): status New Won't Fix
2017-08-04 17:14:33 Steve Langasek maas (Ubuntu Zesty): status New Incomplete
2017-08-04 17:14:45 Steve Langasek maas (Ubuntu Xenial): status New Incomplete
2017-08-04 17:50:50 Andres Rodriguez description [Impact] This is a new upstream release that addresses various upstream bugs. MAAS 2.2.2 does NOT introduce any new features. Please see CHANGELOG for further details. [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 2.2.2 is just a point release that addresses bugs and does not change any behavior. It has minimum risk for backward compatibility issues. It does NOT include any database migrations as such, upgrade risks are very minimal as well. [Impact] This is a new upstream release that addresses various upstream bugs. MAAS 2.2.2 does NOT introduce any new features. Please see CHANGELOG for further details. [Test Case] MAAS testing has been done in various cases, partially documented https://wiki.ubuntu.com/MAASUpdates. This include: All MAAS Upstream releases follow the following testing: 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. Packages from proposed have the following testing to guard against misbuilds: 1. Manual Fresh installation of MAAS 2. Manual upgrade from the previous Ubuntu Release. 3. Manual split region/rack tests. 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 2.2.2 is just a point release that addresses bugs and does not change any behavior. It has minimum risk for backward compatibility issues. It does NOT include any database migrations as such, upgrade risks are very minimal as well.
2017-08-04 17:54:23 Andres Rodriguez description [Impact] This is a new upstream release that addresses various upstream bugs. MAAS 2.2.2 does NOT introduce any new features. Please see CHANGELOG for further details. [Test Case] MAAS testing has been done in various cases, partially documented https://wiki.ubuntu.com/MAASUpdates. This include: All MAAS Upstream releases follow the following testing: 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. Packages from proposed have the following testing to guard against misbuilds: 1. Manual Fresh installation of MAAS 2. Manual upgrade from the previous Ubuntu Release. 3. Manual split region/rack tests. 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 2.2.2 is just a point release that addresses bugs and does not change any behavior. It has minimum risk for backward compatibility issues. It does NOT include any database migrations as such, upgrade risks are very minimal as well. [Impact] This is a new upstream release that addresses various upstream bugs. MAAS 2.2.2 does NOT introduce any new features. Please see CHANGELOG for further details. [Test Case] MAAS testing has been done in various cases, partially documented https://wiki.ubuntu.com/MAASUpdates. This include: All MAAS Upstream releases follow the following testing: 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. Packages from proposed have the following testing to guard against misbuilds: 1. Manual Fresh installation, configuration and deployment of machines. 2. Manual upgrade from the previous Ubuntu Release (and ensure continued operation) 3. Includes split region/rack tests. 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 2.2.2 is just a point release that addresses bugs and does not change any behavior. It has minimum risk for backward compatibility issues. It does NOT include any database migrations as such, upgrade risks are very minimal as well.
2017-08-04 18:51:22 Andres Rodriguez maas (Ubuntu Xenial): status Incomplete New
2017-08-04 18:51:23 Andres Rodriguez maas (Ubuntu Zesty): status Incomplete New
2017-08-04 19:14:08 Steve Langasek maas (Ubuntu Zesty): status New Fix Committed
2017-08-04 19:14:11 Steve Langasek bug added subscriber SRU Verification
2017-08-04 19:14:14 Steve Langasek tags verification-needed verification-needed-zesty
2017-08-04 19:16:21 Steve Langasek maas (Ubuntu Xenial): status New Fix Committed
2017-08-04 19:16:26 Steve Langasek tags verification-needed verification-needed-zesty verification-needed verification-needed-xenial verification-needed-zesty
2017-08-16 12:48:18 Andres Rodriguez tags verification-needed verification-needed-xenial verification-needed-zesty verification-done verification-done-xenial verification-done-zesty
2017-08-16 15:48:53 Launchpad Janitor maas (Ubuntu Zesty): status Fix Committed Fix Released
2017-08-16 15:48:56 Steve Langasek removed subscriber Ubuntu Stable Release Updates Team
2017-08-16 15:49:11 Launchpad Janitor maas (Ubuntu Xenial): status Fix Committed Fix Released