MAAS deletes image architectures if you delete all images of that architecture
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MAAS | Status tracked in 3.6 | |||||
3.4 |
Won't Fix
|
Low
|
Unassigned | |||
3.5 |
Won't Fix
|
Low
|
Unassigned | |||
3.6 |
Triaged
|
Low
|
Unassigned | |||
maas (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
If you try to import a custom image in maas cli it fails with a cryptic error which turns out to be because of a non-existing architecture.
Upon further investigation, it seems that if you delete all images of a specific architecture the architecture itself disappears and then you cannot add a custom image of that arquitecture again, it will fail.
Workaround is to go back to the images section in the GUI, select some ubuntu image of that architecture, wait for it to download and then re-try adding the custom image which will then work.
This is very non-intuitive for end users, and also it's possible for an airgapped environment to erase all images and then get into a situation where they cannot recover.
My understanding (based on conversations on maas channel) is that this is a known behavior, which makes this is bug report a feature-request to 'fix' this to work in a more intuitive way.
Changed in maas: | |
status: | New → Triaged |
summary: |
- MaaS deletes image architectures if you delete all images of that + MAAS deletes image architectures if you delete all images of that architecture |
Changed in maas: | |
milestone: | 3.4.0 → 3.4.x |
Changed in maas: | |
milestone: | 3.4.x → 3.5.x |
Added project MAAS (previously it was only under ubuntu package maas).