Uploading multiple images from the same ISO results in incorrect names in GUI

[Joseph Handzik]

Using version 3.1.0~beta5-10861-g.52020466a

This bug is with the GUI, but I will provide some CLI output to facilitate triage as well.

Using the instructions contained in this repo, provided for use with NVIDIA's DGX OS: https://github.com/DeepOps/packer-maas/tree/master/dgxos5

Two bundles are built for upload - one for DGX A100 systems, and another for DGX 2 systems.

The upload commands used from the CLI are (redacting the username):

maas <user> boot-resources create name='custom/dgx_a100-5.1' title='NVIDIA DGX-A100 5.1' architecture='amd64/generic' filetype='tgz' base_image=ubuntu/focal content@=./dgxos5_dgx_a100.tar.gz

maas <user> boot-resources create name='custom/dgx2-5.1' title='NVIDIA DGX-2 5.1' architecture='amd64/generic' filetype='tgz' base_image=ubuntu/focal content@=dgxos5_dgx2.tar.gz

Important to know (I think) - both tar.gz files are based on the same ISO, but target different system types via the Packer JSON file (which you can take a look at in the GitHub repo above).

Uploading either of the two bundles by itself results in the correct behavior via the GUI. However, once both tar.gz bundles are uploaded, the UI result is the image named "both-uploaded" in the attached zip file.

However, the output from the CLI command 'maas <user> boot-resources read' appears correct - the images are tracked as distinct (note - the skipped 14 id is because I deleted and recreated the DGX-2 upload to make sure I didn't make a mistake).

    {
        "id": 15,
        "type": "Uploaded",
        "name": "dgx2-5.1",
        "architecture": "amd64/generic",
        "resource_uri": "/MAAS/api/2.0/boot-resources/15/",
        "subarches": "generic",
        "title": "NVIDIA DGX-2 5.1"
    },
    {
        "id": 13,
        "type": "Uploaded",
        "name": "dgx_a100-5.1",
        "architecture": "amd64/generic",
        "resource_uri": "/MAAS/api/2.0/boot-resources/13/",
        "subarches": "generic",
        "title": "NVIDIA DGX-A100 5.1"
    }

When going to delete an image in the GUI, both images open with the "Delete" button presented (see "click-bottom-trashcan" in the zip file).

Clicking delete on the bottom trashcan results in two custom images in the list still - and the names are as one would expect prior to the bug occurring (see "after-clicking-delete-on-bottom-image" in the zip).

Clicking on the top image's trashcan in the GUI does nothing. Clicking delete on the bottom image's trashcan behaves as one would expect (see "after-clicking-bottom-trashcan-second-time"). Once the delete button is clicked for this bottom row, both images disappear from the GUI - there are no more custom images listed.