[2.1, UI] Cloning of options under 'Other images' after implementing a new custom image source

Bug #1648515 reported by Peter Matulis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
High
Unassigned

Bug Description

I had been using a mirror local to my MAAS server (everything, including mirror, on localhost) without issue on MAAS 2.0. After upgrading to 2.1 I modified, without issue, the mirror to take into account the v3 stream and bootloaders. Only Ubuntu images (Xenial and Trusty) were chosen. Yet after changing the URL in the web UI (effectively s/v2/v3), choosing connect, and selecting/downloading the Ubuntu images I got a cloning of the options in the 'Other images' section. See screenshot ('other-images-cloning.png'). Reloading the page did not help.

This is the current directory layout of my mirror:

ubuntu@nisse:/var/www/html/maas/images$ tree -L 4
.
├── ephemeral-v2
│   └── daily
│   ├── streams
│   │   └── v1
│   ├── trusty
│   │   └── amd64
│   └── xenial
│   └── amd64
└── ephemeral-v3
    └── daily
        ├── bootloaders
        │   ├── open-firmware
        │   ├── pxe
        │   └── uefi
        ├── streams
        │   └── v1
        ├── trusty
        │   └── amd64
        └── xenial
            └── amd64

Tags: docteam
Revision history for this message
Peter Matulis (petermatulis) wrote :
summary: - [web UI] Cloning of options under 'Other images' after implementing a
+ [2.1, UI] Cloning of options under 'Other images' after implementing a
new custom image source
Changed in maas:
importance: Undecided → High
milestone: none → 2.2.0
Revision history for this message
Peter Matulis (petermatulis) wrote :

The options in the web UI have gone back to normal. Possibly due to a resync? Dunno.

Revision history for this message
Lee Trager (ltrager) wrote :

Was MAAS configured to look at both the V2 and V3 stream at the same time? Could you post the output of maas <profile> boot-sources read

Changed in maas:
status: New → Incomplete
Revision history for this message
Peter Matulis (petermatulis) wrote :

No, there is only one field. I don't see how MAAS can look at two sources concurrently.

$ maas $PROFILE boot-sources read
Success.
Machine-readable output follows:
[
    {
        "resource_uri": "/MAAS/api/2.0/boot-sources/3/",
        "id": 3,
        "url": "http://10.248.0.2/maas/images/ephemeral-v3/daily/",
        "keyring_data": "",
        "created": "2016-12-08T14:42:57.325",
        "updated": "2016-12-08T14:42:57.325",
        "keyring_filename": "/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg"
    }
]

Revision history for this message
Peter Matulis (petermatulis) wrote :

I changed this back to 'New' since I provided the requested information.

Changed in maas:
status: Incomplete → New
Changed in maas:
milestone: 2.2.0 → 2.2.x
Revision history for this message
Blake Rouse (blake-rouse) wrote :

I believe this was fixed in 2.2.1 by ltrager he noticed this issue in his branch testing and converted the output of images to list(set(image)) which removes duplicates.

Can you try with latest 2.2 or trunk to see if you can reproduce this issue. I do truly believe that this has been fixed.

Changed in maas:
status: New → Incomplete
no longer affects: maas/2.1
Changed in maas:
milestone: 2.2.x → 2.3.x
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi!

**This is an automated message**

We believe this is may no longer be an issue in the latest MAAS release. Due to the original date of the bug report, we are currently marking it as Invalid. If you believe this bug report still valid against the latest release of MAAS, or if you are still interested in this, please re-open this bug report.

Thanks

Changed in maas:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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