No "failed" transition from "new"

Bug #1386502 reported by Julian Edwards on 2014-10-28
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Julian Edwards

Bug Description

In pserv.log:

2014-10-28 12:47:02+1000 [-] Unhandled Error
        Traceback (most recent call last):
        Failure: provisioningserver.rpc.exceptions.NodeStateViolation: The status of the node is 0; this status cannot be transitioned to a corresponding failed status.

This is with latest trunk. To recreate, I took an existing READY node through commissioning, which I then aborted because it had a problem, so it went back to NEW.

I tried again, saw the same problem and let it run, and then that error appeared.

Related branches

Changed in maas:
status: New → Triaged
importance: Undecided → Critical
milestone: none → 1.7.0
Christian Reis (kiko) wrote :

Is the node now effectively unreachable, or would a commission now work fine and leave the node in COMMISSIONED?

Julian Edwards (julian-edwards) wrote :

It was not unreachable, but it was stuck in NEW with no log entry as to what was going on.

Christian Reis (kiko) on 2014-10-30
Changed in maas:
assignee: nobody → Julian Edwards (julian-edwards)
milestone: 1.7.0 → next
Christian Reis (kiko) on 2014-10-30
Changed in maas:
milestone: next → 1.7.1
Changed in maas:
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers