[SRU] MAAS 2.4.2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
maas (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned |
Bug 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:/
https:/
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:/
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: | updated |
description: | updated |
summary: |
- [SRU] MAAS 2.4.1 + [SRU] MAAS 2.4.3 |
summary: |
- [SRU] MAAS 2.4.3 + [SRU] MAAS 2.4.2 |
Changed in maas (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → High |
description: | updated |
description: | updated |
Changed in maas (Ubuntu): | |
status: | In Progress → Invalid |
Hello Andres, or anyone else affected,
Accepted maas into bionic-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ maas/2. 4.2-7034- g2f5deb8b8- 0ubuntu1 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- bionic to verification- done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- bionic. In either case, without details of your testing we will not be able to proceed.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!