MAAS

Admin cannot acquire machine that failed to deploy without first releasing it

Bug #1930002 reported by Nathaniel W. Turner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Triaged
Low
Unassigned
MAAS 3.5.0

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?

See original description
Nathaniel W. Turner (nturner)
description: updated
Revision history for this message
Björn Tillenius (bjornt) wrote :

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.

Changed in maas:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Jerzy Husakowski (jhusakowski) wrote :

MAAS should offer more flexibility in changing deployment parameters. We want to look at node lifecycle management and state transitions, and it's likely that this particular issue will be addressed together with other lifecycle management issues in a future release.

tags: added: node-lifecycle
Changed in maas:
importance: Medium → Low
milestone: none → 3.5.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.