Comment 2 for bug 1969510

Revision history for this message
Andre Ruiz (andre-ruiz) wrote :

Ways to reproduce:

This WORKS:

1) Install a fresh maas.
2) Download any ubuntu image of x86_64 architecture using GUI
3) Manually add a custom x86_64 image via CLI (say, for example, ESXi)
4) Check it was correctly added as a custom image and is available on the images list when deploying

This does NOT work:

1) Install a fresh maas
2) Download any ubuntu image of x86_64 architecture using GUI (you need to download at least one when installing).
3) Go back to images menu and delete all images of x86_64 architecture (including ubuntu ones)
4) Manually add a custom x86_64 image via CLI (again, for example, and ESXi image)
5) Watch it fail with a cryptic message about "Wrong architecture"

But this will fix the problem:

6) Go back to images screen, download some x86_64 ubuntu image again
7) Manually add a custom x86_64 image via CLI
8) This time it will work again

Problem is that:

- this is very non-intuitive, specially the error message given
- the proposed fix may not be desirable or even possible (i.e. air gapped systems)