MAAS

Abort Commissioning doesn't not set the node back to its original state

Bug #1359275 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Won't Fix
High
Unassigned

Bug Description

I had a node in Ready state, and mistakenly I clicked on the Comissioning button. I quickly realized about this and I clicked on Abort Commissioning. This set the node back to Declared, when it should have set the node back to Ready

Andres Rodriguez (andreserl)
Changed in maas:
assignee: nobody → Raphaël Badin (rvb)
Revision history for this message
Raphaël Badin (rvb) wrote :

Yeah, we need to improve how the 'Abort' buttons work because we can go into 'Commissioning' (and soon 'Deploying') from different states.

Changed in maas:
importance: Undecided → High
status: New → Triaged
assignee: Raphaël Badin (rvb) → nobody
tags: added: node-lifecycle robustness
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Dear user,

This is an automated message.

We believe this bug report is no longer an issue in the latest version of MAAS. For such reason, we are making this issue as Won't Fix. If you believe this issue is still present in the latest version of MAAS, please re-open this bug report.

Changed in maas:
status: Triaged → Won't Fix
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.