can't deploy re-deploy node when it failed deployment, no start node button
Bug #1420895 reported by
Andres Rodriguez
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Wishlist
|
Unassigned | ||
Bug Description
When a machine has failed deployment, there's only a button to 'Stop' a machine, once stopped, there's no 'Start' button so the node cannot be re-deployed.
In order to re-deploy, the node has to be released and acquired again. It should have allowed me to re-deploy form that state.
| description: | updated |
| Changed in maas: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
| milestone: | none → next |
Revision history for this message
| Lee Trager (ltrager) wrote | #1 |
Revision history for this message
| Adam Collard (adam-collard) wrote | #2 |
| Changed in maas: | |
| status: | Triaged → Invalid |
| Changed in maas: | |
| milestone: | next → none |
To post a comment you must log in.
Deployment may fail due to the storage devices changing. I think MAAS should allow a status transition from FAILED_DEPLOYMENT to COMMISSIONING as well.