Bug 769708

Summary:	Some tasks are left in running state
Product:	[Retired] Beaker	Reporter:	Jan Stancek <jstancek>
Component:	scheduler	Assignee:	Nick Coghlan <ncoghlan>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.8	CC:	bpeck, dcallagh, gozen, jburke, mcsontos, mishin, pbunyan, rmancy, stl
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	MC
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-11-07 07:22:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jan Stancek 2011-12-21 20:10:49 UTC

Description of problem:
Some tasks are left in running state, and don't seem to make to it "Completed".
So when recipe is "finished" I have:

Task 1 - Completed
Task 2 - Completed
...
Task M - Running
...
Task N - Completed/Waiting

It appears that tests actually executed, and in "debug/.task_beah_raw" I see listed log files, so I'm assuming, that beah did try to upload these.


Version-Release number of selected component (if applicable):


How reproducible:
sporadicly

Steps to Reproduce:
unknown, my guess would be to run job with many tasks
  
Actual results:
Some tasks are left in running state.

Expected results:
Task should eventually make it to "Completed".


Additional info:

Comment 3 Bill Peck 2011-12-21 20:46:36 UTC

they won't run forever because the watchdog will eventually get them.

Comment 4 Marian Csontos 2011-12-22 09:56:45 UTC

From this console log it looks like transient error between LC and Scheduler:

    http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2011/12/1737/173756/364205/console.log

    'Fault: <Fault 1: "<class \'turbogears.identity.exceptions.IdentityFailure\'>: Please log in first">

Harness tries to repeat calls when there is network error, but it does not repeat all calls when there are errors reported by Scheduler. The problem is we do not want it to stuck on a single call.

There is a Bug 636093 to improve this.

Comment 5 Nick Coghlan 2012-10-17 04:35:29 UTC

Bulk reassignment of issues as Bill has moved to another team.

Comment 6 Min Shin 2012-11-07 07:22:51 UTC

This bugs is closed as it is either not in the current Beaker scope or we could not find sufficient data in the bug report for consideration.
Please feel free to reopen the bug with additional information and/or business cases behind it.