Web API: special_filesystems inexplicably missing from rendered Machine
Bug #1555022 reported by
Gavin Panella
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Gavin Panella |
Bug Description
In a soon-to-be-landed branch lp:~allenap/maas/storage-ramfs-tmpfs-api, the Machine rendered in response to a call to AnonMachinesHan
Related branches
lp:~allenap/maas/storage-node-special-filesystems-websocket-api
- Blake Rouse (community): Approve
-
Diff: 186 lines (+47/-26)6 files modifiedsrc/maasserver/api/tests/test_enlistment.py (+1/-4)
src/maasserver/listener.py (+3/-3)
src/maasserver/models/filesystem.py (+2/-1)
src/maasserver/websockets/handlers/node.py (+18/-16)
src/maasserver/websockets/handlers/tests/test_device.py (+1/-1)
src/maasserver/websockets/handlers/tests/test_machine.py (+22/-1)
Changed in maas: | |
milestone: | none → 2.0.0 |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It appears that special_filesystems needed to appear on the model as well as on the API class. Work in the linked branch exposed special_filesystems as a related-name (to Filesystem) and suddenly this started working.