Machines that fail hardware testing need to be marked broken before they can be recommissioned
Bug #1696285 reported by
Christian Reis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
High
|
Unassigned |
Bug Description
During the process of commissioning hardware, due to bug 1696276, the hardware testing fails and the nodes are marked Failed Testing. When that happens, you can't just tell MAAS to recommission; you need to mark the node Broken, and only then can you tell it to recommission. That's busywork!
That'The transition from Failed Testing to Commissioning should be allowed.
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.3.0 |
Changed in maas: | |
status: | Incomplete → Fix Committed |
no longer affects: | maas/2.2 |
Changed in maas: | |
status: | Fix Committed → Triaged |
Changed in maas: | |
milestone: | 2.3.0 → 2.3.x |
To post a comment you must log in.
Commissioning and testing are separate node states. They can be run independently and have different failure states. MAAS allows nodes to automatically transition from commissioning to testing as both states are often run sequentially. Once commissioning successfully finishes it does not need to be run again unless hardware has changed. So nodes which fail testing only need to be retested, not recommissioned.
Is there a reason you need to rerun commissioning and testing or will just testing suffice?