** Description changed: [Impact] This is a new upstream release that addresses various issues present in 2.3.0. MAAS 2.3.3 fixes various issues that were present on MAAS 2.3.0. https://launchpad.net/maas/+milestone/2.3.1 https://launchpad.net/maas/+milestone/2.3.2 https://launchpad.net/maas/+milestone/2.3.3 + + This point release includes fixes/enhancements for hardware enablement + and to address customer related issues: + + * Bug 1750622 "[feature] Add ability to select the BIOS boot method for + IPMI - To address issues with newer firmware" + + This adds a new option to power manage machines, that are oriented at + addressing changes in upstream hardware firmware's (that have broken + compatibility with older versions). Causes no behavior changes for MAAS + as it continues to do the same. + + Bug 1758760 "[enhancement] Support Lenovo’s new password policy (Lenovo + SR550)" + + Fixes the password generation process for IPMI discovery to consider new + password policies that are being added to newer hardware or firmware + versions. + + Bug 1739761 [adds support to deploy Precise on MAAS 2.3] + + Re-adds the ability to deploy precise, which was dropped on MAAS 2.3 + initially. + + Bug 1730751 "LACP rate fast by default" + + Changes the default LACP rate to fast, which addresses all issues with + bonds our IS department was having. + [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. Since this is a point release, this has been tested thoroughly to confirm that no regressions have been introduced.
** Description changed: [Impact] This is a new upstream release that addresses various issues present in 2.3.0. MAAS 2.3.3 fixes various issues that were present on MAAS 2.3.0. https://launchpad.net/maas/+milestone/2.3.1 https://launchpad.net/maas/+milestone/2.3.2 https://launchpad.net/maas/+milestone/2.3.3 This point release includes fixes/enhancements for hardware enablement and to address customer related issues: * Bug 1750622 "[feature] Add ability to select the BIOS boot method for IPMI - To address issues with newer firmware" This adds a new option to power manage machines, that are oriented at addressing changes in upstream hardware firmware's (that have broken compatibility with older versions). Causes no behavior changes for MAAS as it continues to do the same. Bug 1758760 "[enhancement] Support Lenovo’s new password policy (Lenovo SR550)" Fixes the password generation process for IPMI discovery to consider new password policies that are being added to newer hardware or firmware versions. Bug 1739761 [adds support to deploy Precise on MAAS 2.3] Re-adds the ability to deploy precise, which was dropped on MAAS 2.3 initially. Bug 1730751 "LACP rate fast by default" - Changes the default LACP rate to fast, which addresses all issues with - bonds our IS department was having. - + Changes the default LACP rate to fast, which addresses issues in that + our IS department was facing. Note that this only changes how often the + control packets are set and it is recommended/preferred to be set to + fast, and the use of slow is discouraged. [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. Since this is a point release, this has been tested thoroughly to confirm that no regressions have been introduced. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772010 Title: [SRU] MAAS 2.3.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1772010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
