No "failed" transition from "new"
Bug #1386502 reported by
Julian Edwards
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Julian Edwards | ||
Bug Description
In pserv.log:
2014-10-28 12:47:02+1000 [-] Unhandled Error
Traceback (most recent call last):
Failure: provisioningser
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
lp:~julian-edwards/maas/ignore-failure-from-new-bug-1386502
- Newell Jensen (community): Approve
-
Diff: 38 lines (+10/-0)2 files modifiedsrc/maasserver/models/node.py (+3/-0)
src/maasserver/models/tests/test_node.py (+7/-0)
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → Critical |
| milestone: | none → 1.7.0 |
Revision history for this message
| Christian Reis (kiko) wrote | #1 |
Revision history for this message
| Julian Edwards (julian-edwards) wrote | #2 |
| Changed in maas: | |
| assignee: | nobody → Julian Edwards (julian-edwards) |
| milestone: | 1.7.0 → next |
| 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.
Is the node now effectively unreachable, or would a commission now work fine and leave the node in COMMISSIONED?