API doesn't allow releasing when a node is in Failed Releasing or Failed Disk Erasing

Bug #1384821 reported by Jason Hobbs on 2014-10-23
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
High
Jason Hobbs
1.7
High
Jason Hobbs
Trunk
High
Jason Hobbs

Bug Description

The API doesn't allow releasing when a node is in Failed Releasing or Failed Disk Erasing, even though it's perfectly reasonable to want to attempt the release operation again. The UI does allow Releasing when in these states.

Related branches

Changed in maas:
milestone: none → 1.7.0
status: New → Triaged
assignee: nobody → Jason Hobbs (jason-hobbs)
Changed in maas:
status: Triaged → In Progress

If it's already failed releasing/disk erasing, should we just treat that as
effectively released, and broken?

Jason Hobbs (jason-hobbs) wrote :

It's up to the admin - they can mark a node as broken from there if they want to.

Changed in maas:
status: In Progress → Fix Committed

Hello Jason, or anyone else affected,

Accepted maas into utopic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/maas/1.7.5+bzr3369-0ubuntu1~14.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: added: verification-needed
Andres Rodriguez (andreserl) wrote :

This issue has been verified to work both on upgrade and fresh install, and has been QA'd. Marking verification-done.

tags: added: verification-done
removed: verification-needed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers