Confusing error message when API key is wrong

Bug #1347518 reported by Björn Tillenius
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Newell Jensen

Bug Description

This API used to work:

           maas vmaas nodes new
               architecture=amd64/generic mac_addresses=AA:AA:AA:AA:AA:01
               mac_addresses=22:AA:AA:AA:AA:01 hostname=client01 powertype=virsh
               autodetect_nodegroup=yes

But with 1.6 b6, I get this error:

    u'consumer.' is not a name=value or name@=filename pair

Tags: cli papercut

Related branches

Changed in maas:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Updated title to reflect the actual problem.

summary: - Can't register new nodes using the API with MAAS 1.6 beta6
+ Confusing error message when API key is wrong
no longer affects: maas/1.6
tags: added: cli papercut
Revision history for this message
Newell Jensen (newell-jensen) wrote :

The output below is MaaS 1.6 b6, running in on an lxc container talking to my VMs and I don't see the above problem. Please re-verify or give additional information that would allow me to see this bug.

ubuntu@apiclient-bug:~$ maas vmaas nodes new architecture=amd64/generic mac_addresses=52:54:00:1d:33:2b mac_addresses=52:54:00:7f:8b:a8 powertype=virsh hostname=client01 autodetect_nodegroup=yes
{
    "status": 1,
    "macaddress_set": [
        {
            "resource_uri": "/MAAS/api/1.0/nodes/node-13b2268e-141d-11e4-b076-00163e12e746/macs/52%3A54%3A00%3A1d%3A33%3A2b/",
            "mac_address": "52:54:00:1d:33:2b"
        },
        {
            "resource_uri": "/MAAS/api/1.0/nodes/node-13b2268e-141d-11e4-b076-00163e12e746/macs/52%3A54%3A00%3A7f%3A8b%3Aa8/",
            "mac_address": "52:54:00:7f:8b:a8"
        }
    ],
    "cpu_count": 0,
    "zone": {
        "resource_uri": "/MAAS/api/1.0/zones/default/",
        "name": "default",
        "description": ""
    },
    "routers": null,
    "netboot": true,
    "osystem": "",
    "storage": 0,
    "owner": null,
    "ip_addresses": [],
    "system_id": "node-13b2268e-141d-11e4-b076-00163e12e746",
    "architecture": "amd64/generic",
    "memory": 0,
    "power_type": "",
    "tag_names": [
        "use-fastpath-installer"
    ],
    "hostname": "client01",
    "distro_series": "",
    "resource_uri": "/MAAS/api/1.0/nodes/node-13b2268e-141d-11e4-b076-00163e12e746/"
}

Changed in maas:
assignee: nobody → Newell Jensen (newell-jensen)
Revision history for this message
Newell Jensen (newell-jensen) wrote :

After changing the API key for MaaS (i.e. wrong API key now for the profile 'vmass'):

ubuntu@apiclient-bug:~$ maas vmaas nodes new architecture=amd64/generic mac_addresses=52:54:00:1d:33:2b mac_addresses=52:54:00:7f:8b:a8 powertype=virsh hostname=client01 autodetect_nodegroup=yes
Invalid consumer.

Changed in maas:
status: Triaged → Fix Committed
Changed in maas:
milestone: none → 1.7.0
Changed in maas:
status: Fix Committed → Fix Released
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.