Can 'break' a 'New' node but cannot 'fix' it

Bug #1636601 reported by Peter Matulis on 2016-10-25
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Low
Unassigned

Bug Description

Using 2.0, a node with a status of 'New' was marked 'Broken' yet attempting to 'fix' it resulted in the message:

"The mark fixed action for 1 node failed with error: Unable to be mark fixed because it has not been commissioned successfully."

Logically, then, the user should be prevented from 'breaking' a node unless it has a status of either 'Ready' or 'Deployed', but not 'New'.

Changed in maas:
importance: Undecided → Low
status: New → Triaged
milestone: none → 2.2.0
Changed in maas:
milestone: 2.2.0 → 2.2.x
Andres Rodriguez (andreserl) wrote :

Hi!

**This is an automated message**

We believe this is may no longer be an issue in the latest MAAS release. Due to the original date of the bug report, we are currently marking it as Invalid. If you believe this bug report still valid against the latest release of MAAS, or if you are still interested in this, please re-open this bug report.

Thanks

Changed in maas:
status: Triaged → Invalid
Peter Matulis (petermatulis) wrote :

I still get the same result with 2.4b3 :

"The mark fixed action for failed with error: Unable to be mark fixed because it has not been commissioned successfully."

Note that the message is now missing text "1 node" (i.e "...for 1 node failed...").

Changed in maas:
status: Invalid → New
Andres Rodriguez (andreserl) wrote :

HI Peter,

Just to clarify:

New -> Mark Broken -> Mark fixed # doesn't work because the machine hasn't been commissioned.

Have you tried?

New -> Mark Broken -> Commission

Changed in maas:
status: New → Incomplete
milestone: 2.2.x → 2.4.x
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers