[SRU] SRU New upstream bugfix release of MAAS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
maas (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
This new upstream bugfix release of MAAS includes bug fixes for several bugs reports. This includes Hardware Enablement for the Cisco B Series.
- Hardware Enablement for Cisco B-Series. (LP: #1300476)
- Allow AMT power type to specify IP Address. (LP: #1308772)
- Spurious failure when starting and creating lock files. (LP: 1308069)
- Fix regression introduced by a security fix (LP: #1311433, LP: #1311433)
- Fix usage of hardware enablement kernels by fixing the preseeds
(LP: #1310082, LP: #1310076, LP: #1310082)
- Fix parallel juju deployments. (LP: #1314409)
- Clear distro_series when stopping node from WebUI (LP: #1316396)
- Fix click hijacking (LP: #1298784)
- Fix blocking API client when deleting a resource (LP: #1313556)
- Do not import Trusty RC images by default (LP: #1311151)
[Test Case]
1. Install MAAS
2. Follow steps for each of the bugs being fixed above.
[Regression Potential]
Minimal. All of the fixes include their own unittests as well as have been tested in the MAAS CI.
Related branches
Changed in maas (Ubuntu): | |
importance: | Undecided → Critical |
tags: |
added: verification-done removed: verification-needed |
Changed in maas (Ubuntu): | |
status: | New → Fix Released |
Hello Andres, or anyone else affected,
Accepted maas into trusty-proposed. The package will build now and be available at http:// launchpad. net/ubuntu/ +source/ maas/1. 5.1+bzr2269- 0ubuntu0. 1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed. In either case, details of your testing will help us make a better decision.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!