[2.1] 400 BAD REQUEST: Unrecognised signature: method=GET op=is_registered
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Blake Rouse |
Bug Description
MAAS API client has "machines is-registered" subcommand, but it does not work with "400 BAD REQUEST". "method=GET op=is_registered" is not in the API document either:
https:/
$ maas "$PROFILE" machines is-registered mac_address=
400 BAD REQUEST
Transfer-
X-Frame-
Unrecognised signature: method=GET op=is_registered
$ apt policy maas
maas:
Installed: 2.1.2+bzr5555-
Candidate: 2.1.2+bzr5555-
Version table:
*** 2.1.2+bzr5555-
500 http://
500 http://
100 /var/lib/
Related branches
- Newell Jensen (community): Approve
-
Diff: 66 lines (+25/-6)2 files modifiedsrc/maasserver/api/nodes.py (+24/-5)
src/maasserver/api/tests/test_nodes.py (+1/-1)
summary: |
- 400 BAD REQUEST: Unrecognised signature: method=GET op=is_registered + [2.1] 400 BAD REQUEST: Unrecognised signature: method=GET + op=is_registered |
Changed in maas: | |
importance: | Medium → High |
milestone: | none → 2.2.0rc2 |
Changed in maas: | |
status: | Confirmed → In Progress |
assignee: | nobody → Blake Rouse (blake-rouse) |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
That's really strange, since in theory the CLI is generated from the API