When a custom image is added, multiple OS entries are created for it

Bug #1431156 reported by Andres Rodriguez
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Invalid
High
Unassigned

Bug Description

I added a custom image to maas 1.8alpha6 and when trying to deploy in the bulk action, selecting the OS yields 5 different/items in the combo list saying 'custom'.

Revision history for this message
Blake Rouse (blake-rouse) wrote :

I have see this sometimes when I have multiple images, and sometimes not. I don't know why, but will look into the issue.

Changed in maas:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Blake Rouse (blake-rouse)
milestone: none → next
Changed in maas:
assignee: Blake Rouse (blake-rouse) → Ricardo Bánffy (rbanffy)
Revision history for this message
Ricardo Bánffy (rbanffy) wrote :

I was unable to replicate the problem.

I ran "make run" from a fresh checkout (3737, after running "make sampledata"). I downloaded a Precise ephemeral image and uploaded it ("maas maas-dev-admin boot-resources create name=custom1 architecture=amd64/generic filetype=tgz content@=./Downloads/precise-ephemeral-maas-amd64.tar.gz") repeatedly (changing the name) without visible issues except when attempting to deploy a node. OS select showed "Custom" but none of my custom images populated the second select.

I'll set up a fresh VM and install the packages generated from this tree and re-run these tests.

If anyone can consistently replicate the issue of did experience it with a different procedure, let me know.

Changed in maas:
status: Triaged → Incomplete
Changed in maas:
status: Incomplete → Triaged
status: Triaged → Incomplete
Gavin Panella (allenap)
Changed in maas:
assignee: Ricardo Bánffy (rbanffy) → nobody
Changed in maas:
milestone: next → 2.3.0rc2
Revision history for this message
Björn Tillenius (bjornt) wrote :

Is this still an issue? I remember fixing this (or at least something similar) a while ago.

Revision history for this message
Jeff Lane  (bladernr) wrote :

I'm no longer able to reproduce this on 2.3.0 beta 3

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Marking invalid until it can be reproduced.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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