`machines creates` complain about invalid architecture while it's in fact missing an image

Bug #2019235 reported by Simon Déziel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Triaged
Medium
Unassigned

Bug Description

Immediately after initializing MAAS, running this `machines create`:

maas admin machines create architecture=amd64/generic mac_addresses=00:16:3e:78:38:78 power_type=lxd power_parameters_project=lxd-cloud power_parameters_certificate="-----BEGIN CERTIFICATE-----...-----END CERTIFICATE-----" power_parameters_key="-----BEGIN PRIVATE KEY-----...-----END PRIVATE KEY-----" power_parameters_password="" power_parameters_power_address=172.24.27.200 power_parameters_instance_name=vm01 hostname=vm01

fails with:
{"architecture": ["'amd64/generic' is not a valid architecture. It should be one of: ''."]}

Apparently, the architecture isn't the actual problem but I'd be missing an image.

Additional information:

# snap list maas maas-test-db
Name Version Rev Tracking Publisher Notes
maas 3.3.3-13184-g.3e9972c19 27405 3.3/stable canonical✓ -
maas-test-db 14.2-29-g.ed8d7f2 131 3.3/stable canonical✓ -

# lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04

Revision history for this message
Simon Déziel (sdeziel) wrote (last edit ):

When the `machines create` fails, here's what I get:

# maas admin boot-resources read
Success.
Machine-readable output follows:
[
    {
        "id": 1,
        "type": "Synced",
        "name": "ubuntu/focal",
        "architecture": "amd64/ga-20.04",
        "resource_uri": "/MAAS/api/2.0/boot-resources/1/",
        "subarches": "generic,hwe-p,hwe-q,hwe-r,hwe-s,hwe-t,hwe-u,hwe-v,hwe-w,ga-16.04,ga-16.10,ga-17.04,ga-17.10,ga-18.04,ga-18.10,ga-19.04,ga-19.10,ga-20.04"
    },
    {
        "id": 2,
        "type": "Synced",
        "name": "ubuntu/focal",
        "architecture": "amd64/ga-20.04-lowlatency",
        "resource_uri": "/MAAS/api/2.0/boot-resources/2/",
        "subarches": "generic,hwe-p,hwe-q,hwe-r,hwe-s,hwe-t,hwe-u,hwe-v,hwe-w,ga-16.04,ga-16.10,ga-17.04,ga-17.10,ga-18.04,ga-18.10,ga-19.04,ga-19.10,ga-20.04"
    },
    {
        "id": 3,
        "type": "Synced",
        "name": "ubuntu/focal",
        "architecture": "amd64/hwe-20.04",
        "resource_uri": "/MAAS/api/2.0/boot-resources/3/",
        "subarches": "generic,hwe-p,hwe-q,hwe-r,hwe-s,hwe-t,hwe-u,hwe-v,hwe-w,ga-16.04,ga-16.10,ga-17.04,ga-17.10,ga-18.04,ga-18.10,ga-19.04,ga-19.10,ga-20.04"
    },
    {
        "id": 4,
        "type": "Synced",
        "name": "ubuntu/focal",
        "architecture": "amd64/hwe-20.04-edge",
        "resource_uri": "/MAAS/api/2.0/boot-resources/4/",
        "subarches": "generic,hwe-p,hwe-q,hwe-r,hwe-s,hwe-t,hwe-u,hwe-v,hwe-w,ga-16.04,ga-16.10,ga-17.04,ga-17.10,ga-18.04,hwe-18.10,hwe-19.04,hwe-19.10,hwe-20.04"
    },
    {
        "id": 5,
        "type": "Synced",
        "name": "ubuntu/focal",
        "architecture": "amd64/hwe-20.04-lowlatency",
        "resource_uri": "/MAAS/api/2.0/boot-resources/5/",
        "subarches": "generic,hwe-p,hwe-q,hwe-r,hwe-s,hwe-t,hwe-u,hwe-v,hwe-w,ga-16.04,ga-16.10,ga-17.04,ga-17.10,ga-18.04,ga-18.10,ga-19.04,ga-19.10,ga-20.04"
    },
    {
        "id": 6,
        "type": "Synced",
        "name": "ubuntu/focal",
        "architecture": "amd64/hwe-20.04-lowlatency-edge",
        "resource_uri": "/MAAS/api/2.0/boot-resources/6/",
        "subarches": "generic,hwe-p,hwe-q,hwe-r,hwe-s,hwe-t,hwe-u,hwe-v,hwe-w,ga-16.04,ga-16.10,ga-17.04,ga-17.10,ga-18.04,hwe-18.10,hwe-19.04,hwe-19.10,hwe-20.04"
    }
]

Revision history for this message
Christian Grabowski (cgrabowski) wrote :

As mentioned in the original report, this is due to images not being synced yet. We should probably error out earlier when images haven't been synced with a message specifying such. Marking as triaged.

Changed in maas:
status: New → Triaged
importance: Undecided → Medium
milestone: none → 3.4.0
Alberto Donato (ack)
Changed in maas:
milestone: 3.4.0 → 3.4.x
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.