Nodes can be in Ready state without commissioning data, if you mark a node in 'failed commisioning' broken and then fixed.
Bug #1402100 reported by
Jason Hobbs
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Blake Rouse |
Bug Description
When you start commissioning on a node, it immediately deletes the old commissioning results, like lshw output. Then if the commissioning fails, and you mark the node as broken, then as fixed again, the node will be 'Ready' but it won't have commissioning data and will fail to install and boot properly.
Related branches
lp:~blake-rouse/maas/fix-1402100
- Mike Pontillo (community): Approve
- Ricardo Bánffy (community): Approve
-
Diff: 108 lines (+61/-0)2 files modifiedsrc/maasserver/node_action.py (+22/-0)
src/maasserver/tests/test_node_action.py (+39/-0)
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → next |
Changed in maas: | |
milestone: | next → 1.8.0 |
no longer affects: | maas/1.7 |
Changed in maas: | |
importance: | High → Critical |
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.
What is using the commissioning data that is causing it to fail to boot? I have not seen this be an issue myself.