[2.2, 2.3, API] Adding a CentOS image via CLI doesn't categorize it correctly

Bug #1701694 reported by Andres Rodriguez on 2017-06-30
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
High
Lee Trager
2.2
High
Unassigned

Bug Description

I've tried adding a centos image via the CLI like:

maas admin boot-resources create name=centos/centos7-105.2 architecture=amd64/generic content@=centos7

And the result is this:

1. On Images listing page:
 - See image under "Generated" images.
 - The name in the UI is shown as "centos/centos7-105.2"

2. Can't deploy image
 - I can't deploy the image (it is not available in the drop-down option).

The expected result of this is:

1. Images to show under "CentOS" section
2. Name to be show as "centos7-105.2"
3. Image to be available to deploy under "CentOS"

when adding a centos image with name=<os>/<name> it should assume that this image is a centos image.

Related branches

Changed in maas:
importance: Undecided → High
assignee: nobody → Lee Trager (ltrager)
milestone: none → 2.3.0
status: New → Triaged
Changed in maas:
status: Triaged → Fix Committed
Changed in maas:
milestone: 2.3.0 → 2.3.0alpha1
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers