Admin cannot acquire machine that failed to deploy without first releasing it
Bug #1930002 reported by
Nathaniel W. Turner
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MAAS | Status tracked in 3.6 | |||||
3.5 |
Won't Fix
|
Low
|
Unassigned | |||
3.6 |
Triaged
|
Low
|
Unassigned |
Bug Description
MAAS 3.0-rc1. Personal severity level: "not a big deal"
A newly-commissioned machine failed to deploy because the storage config was wrong.
The only way to fix this was to first Release the machine back to the pool and then quickly Acquire it before anyone else tried to deploy it.
Could perhaps "Abort..." be an available action for nodes in the "Failed to deploy" state, allowing them to transition directly to Allocated?
I think going from Failed Deployment to Acquired makes sense. We have a similar case, that you should be able to release a Deployed node and have it got to Acquired rather than Ready.