Devices API: claim-sticky-ip-address should return an error when it fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
High
|
Unassigned |
Bug Description
Using the device api with claim-sticky-
$ maas maas device claim-sticky-
Success.
Machine-readable output follows:
{
"macaddress
{
}
],
"zone": {
"name": "default",
},
"parent": null,
"ip_addresses": [],
"hostname": "leading-
"tag_names": [],
"owner": "maas-admin",
"system_id": "node-01b8aa28-
"resource_uri": "/MAAS/
}
Subsequently reading the device also shows an empty ip_addresses.
Using dailybuilds:
$ dpkg -l '*maas*'|cat
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 1.9.0~alpha1+
ii maas-cli 1.9.0~alpha1+
ii maas-cluster-
ii maas-common 1.9.0~alpha1+
ii maas-dhcp 1.9.0~alpha1+
ii maas-dns 1.9.0~alpha1+
ii maas-proxy 1.9.0~alpha1+
ii maas-region-
ii maas-region-
ii python-django-maas 1.9.0~alpha1+
ii python-maas-client 1.9.0~alpha1+
ii python-
Changed in maas: | |
status: | Invalid → New |
Changed in maas: | |
milestone: | none → 1.8.4 |
status: | New → Triaged |
Changed in maas: | |
importance: | Undecided → High |
milestone: | 1.8.4 → next |
summary: |
- Devices API: claim-sticky-ip-address appears not to work + Devices API: claim-sticky-ip-address should return an error when it + fails |
Changed in maas: | |
milestone: | next → 1.9.3 |
milestone: | 1.9.3 → none |
no longer affects: | maas/1.8 |
no longer affects: | maas/1.9 |
Changed in maas: | |
milestone: | none → 1.9.2 |
Changed in maas: | |
milestone: | 1.9.2 → 1.9.3 |
Changed in maas: | |
milestone: | 1.9.3 → 1.9.4 |
Changed in maas: | |
milestone: | 1.9.4 → 1.9.5 |
Hi Michael,
Can you confirm this issue appear sin 1.8 and*not* in 1.9? 1.9 has not been officially released and this side of hte code is being worked on. This means that I'll makr this invalid until confirmed it is actually affecting 1.8 and not 1.9.