NodeManager.start_nodes() is not atomic and has no way to report the exact failures for individual nodes
Bug #1330762 reported by
Julian Edwards
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
High
|
Unassigned | ||
Bug Description
If a StartNode action raises a NodeActionError, start_nodes() currently can't do much about it as its signature is just to return processed nodes with no detail for why the failed ones did fail. In the case of running out of static IP addresses it currently just halts processing.
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| tags: | added: robustness |
| Changed in maas: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
