Switching from Ubuntu version to another leaves the selected kernel version stuck, resulting in incorrect path
Bug #1937274 reported by
Christian Grabowski
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MAAS | Status tracked in 3.6 | |||||
3.3 |
Won't Fix
|
Medium
|
Unassigned | |||
3.4 |
Won't Fix
|
Medium
|
Unassigned | |||
3.5 |
Won't Fix
|
Medium
|
Unassigned | |||
3.6 |
Triaged
|
Medium
|
Unassigned |
Bug Description
Related thread here: https:/
When commissioning a machine with one given version, for instance, Bionic, and then switching to another version, say Focal, and a minimum kernel version was selected, the UI will display no minimum kernel is selected, while the prior kernel version is in fact selected, leading to invalid paths for the given kernel.
Changed in maas: | |
status: | New → Confirmed |
Changed in maas: | |
status: | Confirmed → Triaged |
Changed in maas: | |
milestone: | 3.3.0 → 3.4.0 |
no longer affects: | maas/3.3 |
Changed in maas: | |
milestone: | 3.4.0 → 3.4.x |
Changed in maas: | |
milestone: | 3.4.x → 3.5.x |
To post a comment you must log in.
This is impactful to my company's environment for the following reasons
1. Many machine were built a year ago or more using 18.x as the commission/ ephemeral image. (4000 machines at least)
2. New machines have required 20.x in order to detect the hardware
3. We don't deploy Ubuntu, so the options to pick during deploy/erase/etc are NOT available
The only way to remediate this is to either:
1. Manually edit each node's hwe entry to match the current comission version
2. Create symlinks in the image directories that redirect systems looking for wrong A in right B, which feels like it could end up causing issues later down the line.