Bug 995000 - Recurring events are not detected and cause never-ending job
Summary: Recurring events are not detected and cause never-ending job
Keywords:
Status: CLOSED DUPLICATE of bug 954219
Alias: None
Product: Beaker
Classification: Retired
Component: lab controller
Version: 0.14
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-08 11:37 UTC by Marian Ganisin
Modified: 2018-02-06 00:41 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-08 21:57:10 UTC
Embargoed:

Attachments (Terms of Use)

Description Marian Ganisin 2013-08-08 11:37:55 UTC 
Description of problem:
Typically during first task (which is most often /distribution/install) some issue may occur that causes that the process is restarted (it can be hardware issue, incorrect boot order setup after installation or whatever). Such jobs can be identified for example by reporting one event/subtask repeatedly, for example:

/distribution/install
  	  ./start
  	  ./start
  	  ./start
  	  ./start
  	  ./start
  	  ./start
  	  ./start
  	  ./start
  	  ./start
...

This causes infinite loop and never-ending job. This seems to be easy to detect and job can be aborted in case of loop.

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

How reproducible:
unclear conditions

Actual results:
Never-ending job stuck in a loop

Expected results:
Recurring event detected, job aborted
Note You need to log in before you can comment on or make changes to this bug.