Bug 705026 - Harness picking existing launcher script causing EWD after reboot
Summary: Harness picking existing launcher script causing EWD after reboot
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: beah
Version: 0.6
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
Assignee: Marian Csontos
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-16 12:50 UTC by Marian Csontos
Modified: 2019-05-22 13:39 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-02 09:47:08 UTC
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.