Bug 1257941 - task is left in running state after rhts-reboot
Summary: task is left in running state after rhts-reboot
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Beaker
Classification: Retired
Component: beah
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard: Misc
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-28 12:33 UTC by Jan Stancek
Modified: 2019-04-12 08:52 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 908354
Environment:
Last Closed: 2019-04-12 08:49:39 UTC
Embargoed:


Attachments (Terms of Use)

Description Jan Stancek 2015-08-28 12:33:11 UTC
+++ This bug was initially created as a clone of Bug #908354 +++

Description of problem:
Task is left in running state after rhts-reboot and following message appears on console:

2015-08-27 21:29:39,137 backend _run_task: ERROR Exception raised when running t 
ask. Setting to finished 
Traceback (most recent call last): 
  File "/usr/lib/python2.7/site-packages/beah/backends/beakerlc.py", line 595, i 
n _run_task 
    thingy.getResult() 
  File "/usr/lib64/python2.7/site-packages/twisted/internet/defer.py", line 870, 
 in getResult 
    self.result.raiseException() 
  File "/usr/lib64/python2.7/site-packages/twisted/python/failure.py", line 370, 
 in raiseException 
    raise self.type, self.value, self.tb 

The problem from Bug #908354 returned. Beah is running /kernel/RHEL6/drivers/3rd-party, which runs rhts-reboot, and after reboot task is skipped and left in running state.

Following message can be seen before reboot takes place:
2015-08-27 20:59:42,953 beah task_finished: INFO Task f32541d0-dbce-488d-9673-23 
4a29b54ef4 has finished. Marking it as done.

Comment 4 Dan Callaghan 2015-08-30 23:28:10 UTC
Jan, have you seen this problem anywhere else besides S/390 guests?

Comment 5 Jan Stancek 2015-08-31 07:01:29 UTC
(In reply to Dan Callaghan from comment #4)
> Jan, have you seen this problem anywhere else besides S/390 guests?

No, as I recall it was always s390 so far.

Comment 6 Tomas Klohna 🔧 2019-04-12 08:49:39 UTC
Hello Jan!
I'm closing this issue as it affects beah. I suggest using restraint.
Please re-open if this issue blocks you.


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