Failure: twisted.internet.defer.CancelledError
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Unassigned | ||
Bug Description
I was trying to abort the commissioning of a handful of nodes and saw that clusterd.log was full of:
2015-03-26 22:02:33+0800 [-] Unhandled Error
Traceback (most recent call last):
Failure: twisted.
2015-03-26 22:02:33+0800 [-] Unhandled Error
Traceback (most recent call last):
Failure: twisted.
2015-03-26 22:02:33+0800 [-] Unhandled Error
Traceback (most recent call last):
Failure: twisted.
2015-03-26 22:02:33+0800 [-] Unhandled Error
Traceback (most recent call last):
Failure: twisted.
2015-03-26 22:02:33+0800 [-] Unhandled Error
Traceback (most recent call last):
Failure: twisted.
2015-03-26 22:02:33+0800 [-] Unhandled Error
Traceback (most recent call last):
Failure: twisted.
2015-03-26 22:02:33+0800 [-] Unhandled Error
Traceback (most recent call last):
Failure: twisted.
Not exactly sure where it comes from (there is no proper indication of the source of the problem). I guess the first step is to improve the logging so that we can then pinpoint precisely where the problem is. Marking this critical as this seems to be a crash.
Related branches
- Raphaël Badin (community): Approve
-
Diff: 306 lines (+115/-41)2 files modifiedsrc/provisioningserver/rpc/power.py (+46/-22)
src/provisioningserver/rpc/tests/test_power.py (+69/-19)
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
