Bug 1004381 - [Beaker] backend.twisted emit: ERROR Unhandled error in Deferred:
Summary: [Beaker] backend.twisted emit: ERROR Unhandled error in Deferred:
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: beah
Version: 0.14
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 0.14.3
Assignee: Amit Saha
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-04 14:08 UTC by PaulB
Modified: 2018-02-06 00:41 UTC (History)
12 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-12-19 06:11:14 UTC
Embargoed:


Attachments (Terms of Use)

Comment 3 Amit Saha 2013-10-24 03:36:46 UTC
When there are no remaining tasks, a NothingToDoException is raised in beakerlc.py:

 raise NothingToDoException("No more tasks in recipe.")

So it seems that the second point in the answer here [1] may have a clue.
[1] http://stackoverflow.com/questions/3826233/twisted-no-exception-trace-if-error-from-a-callback

Comment 5 Amit Saha 2013-11-01 06:41:17 UTC
(In reply to Amit Saha from comment #3)
> When there are no remaining tasks, a NothingToDoException is raised in
> beakerlc.py:
> 
>  raise NothingToDoException("No more tasks in recipe.")

http://gerrit.beaker-project.org/#/c/2442/

Comment 7 Amit Saha 2013-11-05 04:05:35 UTC
Verification suggestions:

To verify this bug, you will have to monitor the console.log (if running in an environment where conserver is set up properly), or stare at the console.

If you are running only the /distribution/install, the console logs should not contain any "ERROR unhandled.." messages after the task is complete and just before the machine is turned off.

If you are running only the /distribution/install and reservesys task, the console logs should not contain any "ERROR unhandled.." messages after you execute 'return2beaker.sh'.

PS: Note that there are other messages from Twisted that will be all over, so, you have to be careful (not applicable if console.log is available).


Note You need to log in before you can comment on or make changes to this bug.