Users are able to change the os and release when node is not acquired
Bug #1378936 reported by
Blake Rouse
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Newell Jensen |
Bug Description
Currently a user can change the os and release without the node being allocated. This should not be allowed until the node is allocated.
Related branches
lp://qastaging/~newell-jensen/maas/fix-bug-1378936
- Jeroen T. Vermeulen (community): Approve
-
Diff: 378 lines (+109/-69)4 files modifiedsrc/maasserver/forms.py (+41/-21)
src/maasserver/templates/maasserver/node_edit.html (+16/-14)
src/maasserver/tests/test_forms_node.py (+43/-34)
src/maasserver/views/nodes.py (+9/-0)
Changed in maas: | |
assignee: | nobody → Newell Jensen (newell-jensen) |
Changed in maas: | |
milestone: | 1.7.0 → next |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
milestone: | next → 1.7.0 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Isn't this a security problem (DoS)? I think these values only get reset when releasing, right? It would leave a nasty surprise for someone.