Bug 705026

Summary:	Harness picking existing launcher script causing EWD after reboot
Product:	[Retired] Beaker	Reporter:	Marian Csontos <mcsontos>
Component:	beah	Assignee:	Marian Csontos <mcsontos>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	high
Version:	0.6	CC:	bpeck, dcallagh, mcsontos, rmancy, stl
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-02 09:47:08 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 Marian Csontos 2011-05-16 12:50:52 UTC

Description of problem:
Launchers are surviving reboot and these may be picked and finished by rhts-compat service before other components take that into account.

Launchers belong to /var/run which should be wiped out on boot.

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

How reproducible:
Unreliably as any race conditions: Must be a task finishing soon after reboot in combination with "right" timing.

Actual results:
Task is "finished" but harness does not capture the finish.

Expected results:
Task should finish properly and next task should start.

Comment 1 Marian Csontos 2011-05-17 19:12:09 UTC

The proposed solution does not work with el{3,4,5} and it would not get enough testing in this cycle.