MAAS doesn't allow you to select what HWE kernel to use when commissioning
Bug #1490711 reported by
Andres Rodriguez
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Unassigned |
Bug Description
MAAS doesn't allow you to select the HWE kernel to use for commissioning. It, however, allows you to change the MAAS release. It would be nice if MAAS would allow you to change the commissioning release *and* the HWE kernel in use.
1. Global option (global_
2. Machine enlists using global_
3. after enlistment, machine's min_hwe_kernel is set = to min_hwe_
4. commissioning uses node.min_hwe_kernel if set (or generic if none set)
5. deployment uses min_hwe_kernel if set (which is what currently happens)
Related branches
lp:~ltrager/maas/global_min_hwe_kernel
- Blake Rouse (community): Approve
- Andres Rodriguez (community): Needs Information
-
Diff: 367 lines (+140/-5)12 files modifiedsrc/maasserver/api/pxeconfig.py (+12/-1)
src/maasserver/api/tests/test_pxeconfig.py (+20/-0)
src/maasserver/forms.py (+7/-1)
src/maasserver/forms_settings.py (+39/-0)
src/maasserver/models/config.py (+1/-0)
src/maasserver/models/node.py (+6/-0)
src/maasserver/models/tests/test_node.py (+14/-0)
src/maasserver/static/js/angular/controllers/add_hardware.js (+3/-1)
src/maasserver/static/js/angular/factories/general.js (+10/-0)
src/maasserver/static/js/angular/factories/tests/test_general.js (+15/-2)
src/maasserver/tests/test_forms_commissioning.py (+8/-0)
src/maasserver/websockets/handlers/general.py (+5/-0)
Changed in maas: | |
milestone: | none → next |
milestone: | next → 1.9.0 |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
Changed in maas: | |
importance: | Wishlist → High |
Changed in maas: | |
status: | Confirmed → Triaged |
Changed in maas: | |
importance: | High → Critical |
Changed in maas: | |
status: | Triaged → In Progress |
description: | updated |
tags: | added: blocks-hwcert-server |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
tags: | removed: blocks-hwcert-server |
no longer affects: | maas/1.8 |
To post a comment you must log in.
Would it be possible to know that a machine FETCHED a kernel but then FAILED to boot it properly? If so, could we not automagically:
* try the default release kernel, and if needed
* try the next kernel up, and if needed
* keep going through the HWE kernels, then
* record the first one that works?
In this way, we could automagically "just work" when commissioning, automagically remember the needed HWE kernel, but still let someone set the kernel to use as a property of the machine if they want to do it manually?