[2.0b6] Cannot allocate a node based on its system_id
Bug #1590991 reported by
Mike Pontillo
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Mike Pontillo | ||
Bug Description
When using the "machines allocate" API, there was no way to allocate a node based on its system_id. I first had to look up the hostname. (which could change between API calls, so isn't reliable.)
Related bugs:
* bug 1074317: cmdline acquire and start is difficult
Related branches
lp:~mpontillo/maas/node-allocate-by-system-id-plus-doc-fixes-1590991
- Blake Rouse (community): Approve
-
Diff: 117 lines (+58/-2)4 files modifiedsrc/maasserver/api/machines.py (+31/-1)
src/maasserver/api/tests/test_machines.py (+16/-0)
src/maasserver/node_constraint_filter_forms.py (+10/-1)
src/maasserver/tests/test_node_constraint_filter_forms.py (+1/-0)
| Changed in maas: | |
| milestone: | none → 2.0.0 |
Revision history for this message
| Scott Moser (smoser) wrote | #1 |
| description: | updated |
Revision history for this message
| Mike Pontillo (mpontillo) wrote | #2 |
| summary: |
- Cannot allocate a node based on its system_id + [2.0b6] Cannot allocate a node based on its system_id |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
fwiw, this is really a dupe of bug 1074317.