Comment 38 for bug 1519527

I can confirm that I have replicated the issue in my local MAAS test bed.

I'm seeing behavior such as this:

$ maas admin device claim-sticky-ip-address node-ad58adcc-980a-11e5-a692-525400130e6f
Success.
Machine-readable output follows:
{
    "macaddress_set": [
        {
            "mac_address": "01:02:03:04:05:07"
        }
    ],
    "zone": {
        "resource_uri": "/MAAS/api/1.0/zones/default/",
        "name": "default",
        "description": ""
    },
    "parent": "node-0f48bcc8-9263-11e5-9fc7-525400130e6f",
    "ip_addresses": [],
    "hostname": "cheap-coast.maas",
    "system_id": "node-ad58adcc-980a-11e5-a692-525400130e6f",
    "owner": "root",
    "tag_names": [],
    "resource_uri": "/MAAS/api/1.0/devices/node-ad58adcc-980a-11e5-a692-525400130e6f/"
}

I would expect to see some ip_addresses here, but we've got nothing.

I'm still working on the root cause.