changing image source forces re-select all images and architecture individually step by step

Bug #1974480 reported by Patricia Domingues
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

In Our MAAS 3.2.0~beta4 I've got to change the image source to download the Ubuntu 22.10 Kinetic Kudo (development) images, but instead of just adding/selecting that, as usually I did on older MAAS versions, I needed to select each one of the images we already had, one at a time:

22.04 LTS - amd64 - 663.6 MB - Synced
22.04 LTS - arm64 - 757.1 MB - Synced
21.10 - amd64 - 566.5 MB - Synced
21.10 - arm64 - 614.0 MB - Synced
20.04 LTS - amd64 - 1.1 GB - Synced
20.04 LTS - arm64 - 941.8 MB - Synced
18.04 LTS - amd64 - 676.3 MB - Synced
18.04 LTS - arm64 - 550.3 MB - Synced
16.04 LTS - amd64 - 541.0 MB - Synced
16.04 LTS - arm64 - 441.6 MB - Synced

it is because there's a radio/option button for each Ubuntu Release instead of a checkbox (like there're for the architectures)

Revision history for this message
Patricia Domingues (patriciasd) wrote :

adding a screencast of it

Revision history for this message
Patricia Domingues (patriciasd) wrote (last edit ):

in the screencast from comment#1, please ignore the kinetic in the list of available images because I was re-doing that just for recording this :)

tags: added: ui
Changed in maas-ui:
importance: Undecided → Unknown
Changed in maas:
importance: Undecided → Medium
milestone: none → 3.3.0
status: New → Triaged
Changed in maas:
milestone: 3.3.0 → 3.4.0
Alberto Donato (ack)
Changed in maas:
milestone: 3.4.0 → 3.4.x
Revision history for this message
Thorsten Merten (thorsten-merten) wrote :

I am not sure if this is a but. Once you change the image source you might really want to start from scratch. It makes sense to have some UX input to this and possibly move it to the PF board

tags: removed: ui
Changed in maas-ui:
status: New → Triaged
milestone: none → 3.4.x
Revision history for this message
Maximilian Blazek (maximilian-blazek) wrote :

From the screencast, we seem to know that it is the same image because the corresponding row in the image table is updated after the selection. I think depending on how this is determined, it makes sense to pre-select the images or not.
If it's based on a checksum (or similar) and we know it's exactly the same image, it would make sense to automatically select the images.
I think if it's determined based on metadata like the image name, it wouldn't make sense to pre-select because the images might actually be different and it should be a conscious decision by the user to reuse those images. If it turns out that the user needs to re-select the images, we could do a better job of explaining to the user why they need to re-select and verify their selection.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.