| 2018-08-23 15:20:28 |
Andres Rodriguez |
bug |
|
|
added bug |
| 2018-08-23 15:22:15 |
Andres Rodriguez |
description |
[Impact]
This is a new upstream release that addresses various issues present in 2.3.0.
MAAS 2.3.4 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
https://launchpad.net/maas/+milestone/2.3.4
This point release includes fixes/enhancements for hardware enablement and to address customer related issues that are worth noting:
Enhancements/Hardware Enablement
--------------------------------
* 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.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, and this change only takes effect by a user driven action.
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.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, by testing the old password policy. If it doesn't work it will use the new password policy.
LP: #1779712 [enhancement] maas-proxy port should be configurable
Adds the ability to change the proxy port for the proxy that MAAS uses. If users upgrade, the configuration rendered will continue to use the default port. This will only take effect for users who change the port.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, by using the default port. This change only takes effect by a user driven action.
LP: #1778710 [2.3] Allow telling MAAS image import to not use proxy.
Allow's users to tell MAAS to import images without using the configured proxy, in cases that MAAS is directly connected to the internet but machines are not.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, this would only take effect by a user driven action.
Bug fixes that change existing behaviour
------------------------
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 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.
Bug 1767137 "Default install is now importing bionic by default instead of xenial"
This is an issue that MAAS automatically started selection Bionic for commissioning instead of Xenial as it was intended. This ensure that Xenial is selected by default. Note that in case of upgrades, if Bionic is already selected, MAAS won't change this to Xenial. It will *only* affect to new installs.
[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.
Minimal (for deployments).
LP: #1730751 is fixed in this release, which changes the default LACP rate to fast. This doesn't provide any regression for MAAS itself, machines deployed with bonds will have the LACP rate to fast, which will yield discovery of errors much faster.
Since this is a point release, this has been tested thoroughly to confirm that no regressions have been introduced. |
[Impact]
This is a new upstream release that addresses various issues present in 2.4.2.
MAAS 2.4.2 fixes various issues that were present on MAAS 2.4.2.
https://launchpad.net/maas/+milestone/2.4.1
https://launchpad.net/maas/+milestone/2.4.2
This point release includes fixes/enhancements for hardware enablement and to address customer related issues that are worth noting:
Enhancements/Hardware Enablement
--------------------------------
* 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.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, and this change only takes effect by a user driven action.
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.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, by testing the old password policy. If it doesn't work it will use the new password policy.
LP: #1779712 [enhancement] maas-proxy port should be configurable
Adds the ability to change the proxy port for the proxy that MAAS uses. If users upgrade, the configuration rendered will continue to use the default port. This will only take effect for users who change the port.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, by using the default port. This change only takes effect by a user driven action.
LP: #1778710 [2.3] Allow telling MAAS image import to not use proxy.
Allow's users to tell MAAS to import images without using the configured proxy, in cases that MAAS is directly connected to the internet but machines are not.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, this would only take effect by a user driven action.
Bug fixes that change existing behaviour
------------------------
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 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.
Bug 1767137 "Default install is now importing bionic by default instead of xenial"
This is an issue that MAAS automatically started selection Bionic for commissioning instead of Xenial as it was intended. This ensure that Xenial is selected by default. Note that in case of upgrades, if Bionic is already selected, MAAS won't change this to Xenial. It will *only* affect to new installs.
[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.
Minimal (for deployments).
LP: #1730751 is fixed in this release, which changes the default LACP rate to fast. This doesn't provide any regression for MAAS itself, machines deployed with bonds will have the LACP rate to fast, which will yield discovery of errors much faster.
Since this is a point release, this has been tested thoroughly to confirm that no regressions have been introduced. |
|
| 2018-08-23 15:28:02 |
Andres Rodriguez |
description |
[Impact]
This is a new upstream release that addresses various issues present in 2.4.2.
MAAS 2.4.2 fixes various issues that were present on MAAS 2.4.2.
https://launchpad.net/maas/+milestone/2.4.1
https://launchpad.net/maas/+milestone/2.4.2
This point release includes fixes/enhancements for hardware enablement and to address customer related issues that are worth noting:
Enhancements/Hardware Enablement
--------------------------------
* 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.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, and this change only takes effect by a user driven action.
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.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, by testing the old password policy. If it doesn't work it will use the new password policy.
LP: #1779712 [enhancement] maas-proxy port should be configurable
Adds the ability to change the proxy port for the proxy that MAAS uses. If users upgrade, the configuration rendered will continue to use the default port. This will only take effect for users who change the port.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, by using the default port. This change only takes effect by a user driven action.
LP: #1778710 [2.3] Allow telling MAAS image import to not use proxy.
Allow's users to tell MAAS to import images without using the configured proxy, in cases that MAAS is directly connected to the internet but machines are not.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, this would only take effect by a user driven action.
Bug fixes that change existing behaviour
------------------------
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 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.
Bug 1767137 "Default install is now importing bionic by default instead of xenial"
This is an issue that MAAS automatically started selection Bionic for commissioning instead of Xenial as it was intended. This ensure that Xenial is selected by default. Note that in case of upgrades, if Bionic is already selected, MAAS won't change this to Xenial. It will *only* affect to new installs.
[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.
Minimal (for deployments).
LP: #1730751 is fixed in this release, which changes the default LACP rate to fast. This doesn't provide any regression for MAAS itself, machines deployed with bonds will have the LACP rate to fast, which will yield discovery of errors much faster.
Since this is a point release, this has been tested thoroughly to confirm that no regressions have been introduced. |
[Impact]
This is a new upstream release that addresses various issues present in 2.4.2.
MAAS 2.4.2 fixes various issues that were present on MAAS 2.4.2.
https://launchpad.net/maas/+milestone/2.4.1
https://launchpad.net/maas/+milestone/2.4.2
This point release includes fixes/enhancements for hardware enablement and to address customer related issues that are worth noting:
Enhancements
------------
LP: #1779712 [enhancement] maas-proxy port should be configurable
Adds the ability to change the proxy port for the proxy that MAAS uses. If users upgrade, the configuration rendered will continue to use the default port. This will only take effect for users who change the port.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, by using the default port. This change only takes effect by a user driven action.
LP: #1778710 [2.3] Allow telling MAAS image import to not use proxy.
Allow's users to tell MAAS to import images without using the configured proxy, in cases that MAAS is directly connected to the internet but machines are not.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, this would only take effect by a user driven action.
Resource Pools UI - MAAS 2.4.1 adds API & UI for resource pools. Al
Regression potential: Minimal. This is minimal because it doesn't affect the current operation provided that everything already released in 2.4.0 already included the resource pools feature. This only adds the missing API endpoints and UI that's already been released in 2.5.
[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.
Minimal (for deployments).
LP: #1730751 is fixed in this release, which changes the default LACP rate to fast. This doesn't provide any regression for MAAS itself, machines deployed with bonds will have the LACP rate to fast, which will yield discovery of errors much faster.
Since this is a point release, this has been tested thoroughly to confirm that no regressions have been introduced. |
|
| 2018-08-23 15:30:44 |
Andres Rodriguez |
summary |
[SRU] MAAS 2.4.1 |
[SRU] MAAS 2.4.3 |
|
| 2018-08-23 15:30:47 |
Andres Rodriguez |
summary |
[SRU] MAAS 2.4.3 |
[SRU] MAAS 2.4.2 |
|
| 2018-08-23 15:33:11 |
Andres Rodriguez |
maas (Ubuntu): status |
New |
In Progress |
|
| 2018-08-23 15:33:13 |
Andres Rodriguez |
maas (Ubuntu): importance |
Undecided |
High |
|
| 2018-08-23 15:35:43 |
Andres Rodriguez |
description |
[Impact]
This is a new upstream release that addresses various issues present in 2.4.2.
MAAS 2.4.2 fixes various issues that were present on MAAS 2.4.2.
https://launchpad.net/maas/+milestone/2.4.1
https://launchpad.net/maas/+milestone/2.4.2
This point release includes fixes/enhancements for hardware enablement and to address customer related issues that are worth noting:
Enhancements
------------
LP: #1779712 [enhancement] maas-proxy port should be configurable
Adds the ability to change the proxy port for the proxy that MAAS uses. If users upgrade, the configuration rendered will continue to use the default port. This will only take effect for users who change the port.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, by using the default port. This change only takes effect by a user driven action.
LP: #1778710 [2.3] Allow telling MAAS image import to not use proxy.
Allow's users to tell MAAS to import images without using the configured proxy, in cases that MAAS is directly connected to the internet but machines are not.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, this would only take effect by a user driven action.
Resource Pools UI - MAAS 2.4.1 adds API & UI for resource pools. Al
Regression potential: Minimal. This is minimal because it doesn't affect the current operation provided that everything already released in 2.4.0 already included the resource pools feature. This only adds the missing API endpoints and UI that's already been released in 2.5.
[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.
Minimal (for deployments).
LP: #1730751 is fixed in this release, which changes the default LACP rate to fast. This doesn't provide any regression for MAAS itself, machines deployed with bonds will have the LACP rate to fast, which will yield discovery of errors much faster.
Since this is a point release, this has been tested thoroughly to confirm that no regressions have been introduced. |
[Impact]
This is a new upstream release that addresses various issues present in 2.4.2.
MAAS 2.4.2 fixes various issues that were present on MAAS 2.4.2.
https://launchpad.net/maas/+milestone/2.4.1
https://launchpad.net/maas/+milestone/2.4.2
This point release includes fixes/enhancements for hardware enablement and to address customer related issues that are worth noting:
Enhancements
------------
LP: #1779712 [enhancement] maas-proxy port should be configurable
Adds the ability to change the proxy port for the proxy that MAAS uses. If users upgrade, the configuration rendered will continue to use the default port. This will only take effect for users who change the port.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, by using the default port. This change only takes effect by a user driven action.
LP: #1778710 [2.3] Allow telling MAAS image import to not use proxy.
Allow's users to tell MAAS to import images without using the configured proxy, in cases that MAAS is directly connected to the internet but machines are not.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, this would only take effect by a user driven action.
Resource Pools UI - MAAS 2.4.1 adds API & UI for resource pools. Al
Regression potential: Minimal. This is minimal because it doesn't affect the current operation provided that everything already released in 2.4.0 already included the resource pools feature. This only adds the missing API endpoints and UI that's already been released in 2.5.
Remote authentication - Adds improvements to remote authentication support.
Regression potential: Minimal, given that this is never enabled. This fixes the support for remote authentication against idm.
[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.
Minimal (for deployments).
LP: #1730751 is fixed in this release, which changes the default LACP rate to fast. This doesn't provide any regression for MAAS itself, machines deployed with bonds will have the LACP rate to fast, which will yield discovery of errors much faster.
Since this is a point release, this has been tested thoroughly to confirm that no regressions have been introduced. |
|
| 2018-08-23 15:36:41 |
Andres Rodriguez |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-08-23 15:38:49 |
Andres Rodriguez |
description |
[Impact]
This is a new upstream release that addresses various issues present in 2.4.2.
MAAS 2.4.2 fixes various issues that were present on MAAS 2.4.2.
https://launchpad.net/maas/+milestone/2.4.1
https://launchpad.net/maas/+milestone/2.4.2
This point release includes fixes/enhancements for hardware enablement and to address customer related issues that are worth noting:
Enhancements
------------
LP: #1779712 [enhancement] maas-proxy port should be configurable
Adds the ability to change the proxy port for the proxy that MAAS uses. If users upgrade, the configuration rendered will continue to use the default port. This will only take effect for users who change the port.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, by using the default port. This change only takes effect by a user driven action.
LP: #1778710 [2.3] Allow telling MAAS image import to not use proxy.
Allow's users to tell MAAS to import images without using the configured proxy, in cases that MAAS is directly connected to the internet but machines are not.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, this would only take effect by a user driven action.
Resource Pools UI - MAAS 2.4.1 adds API & UI for resource pools. Al
Regression potential: Minimal. This is minimal because it doesn't affect the current operation provided that everything already released in 2.4.0 already included the resource pools feature. This only adds the missing API endpoints and UI that's already been released in 2.5.
Remote authentication - Adds improvements to remote authentication support.
Regression potential: Minimal, given that this is never enabled. This fixes the support for remote authentication against idm.
[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.
Minimal (for deployments).
LP: #1730751 is fixed in this release, which changes the default LACP rate to fast. This doesn't provide any regression for MAAS itself, machines deployed with bonds will have the LACP rate to fast, which will yield discovery of errors much faster.
Since this is a point release, this has been tested thoroughly to confirm that no regressions have been introduced. |
[Impact]
This is a new upstream release that addresses various issues present in 2.4.2.
MAAS 2.4.2 fixes various issues that were present on MAAS 2.4.2.
https://launchpad.net/maas/+milestone/2.4.1
https://launchpad.net/maas/+milestone/2.4.2
This point release includes fixes/enhancements for hardware enablement and to address customer related issues that are worth noting:
Enhancements
------------
LP: #1779712 [enhancement] maas-proxy port should be configurable
Adds the ability to change the proxy port for the proxy that MAAS uses. If users upgrade, the configuration rendered will continue to use the default port. This will only take effect for users who change the port.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, by using the default port. This change only takes effect by a user driven action.
LP: #1778710 [2.3] Allow telling MAAS image import to not use proxy.
Allow's users to tell MAAS to import images without using the configured proxy, in cases that MAAS is directly connected to the internet but machines are not.
Regression potential: None. MAAS will continue to behave the same way it did before in new installs and upgrades, this would only take effect by a user driven action.
Resource Pools UI - MAAS 2.4.1 adds API & UI for resource pools. Al
Regression potential: Minimal. This is minimal because it doesn't affect the current operation provided that everything already released in 2.4.0 already included the resource pools feature. This only adds the missing API endpoints and UI that's already been released in 2.5.
Remote authentication - Adds improvements to remote authentication support.
Regression potential: Minimal, given that this is never enabled. This fixes the support for remote authentication against idm.
[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. |
|
| 2018-08-30 12:27:43 |
Łukasz Zemczak |
maas (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2018-08-30 12:27:45 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2018-08-30 12:27:48 |
Łukasz Zemczak |
tags |
|
verification-needed verification-needed-bionic |
|
| 2018-09-05 22:57:53 |
Andres Rodriguez |
tags |
verification-needed verification-needed-bionic |
verification-done verification-done-bionic |
|
| 2018-09-06 08:46:53 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2018-09-06 08:56:57 |
Launchpad Janitor |
maas (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-04-20 12:58:20 |
Andres Rodriguez |
maas (Ubuntu): status |
In Progress |
Invalid |
|
