Transition from New -> Commissioning should throw an error if node power is on
Bug #1457990 reported by
Mike Pontillo
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Medium
|
Blake Rouse | ||
Bug Description
When a node in "New" state is commissioned, the commissioning will fail if the node is powered on.
This is intentional, since the node may have been added to MAAS accidentally.
The current behavior is that the node is "stuck" in "Commissioning" state. However, now that the following MP has landed, this is inconsistent with the behavior we get when we re-deploy a node in "Fixed" state when the power is already on:
https:/
Suggestion: if the user attempts to commission a new node, throw an error (similar to the noted MP) if the power is already on.
Related branches
lp:~blake-rouse/maas/fix-1457990
- Mike Pontillo (community): Approve
-
Diff: 42 lines (+13/-1)2 files modifiedsrc/maasserver/node_action.py (+3/-0)
src/maasserver/tests/test_node_action.py (+10/-1)
| Changed in maas: | |
| milestone: | none → 1.8.0 |
| Changed in maas: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Blake Rouse (blake-rouse) |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
