Bug 851897 - recipe's watchdog status grouped by recipe_set
Summary: recipe's watchdog status grouped by recipe_set
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Beaker
Classification: Retired
Component: lab controller
Version: 0.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nick Coghlan
QA Contact:
URL:
Whiteboard: MC
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-27 01:29 UTC by Raymond Mancy
Modified: 2014-12-08 01:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-29 00:10:16 UTC
Embargoed:

Attachments (Terms of Use)

Description Raymond Mancy 2012-08-27 01:29:56 UTC 
In a multi-recipe recipeset, the status of any recipe is potentially determined by the status of another recipe in the same recipeset.

It seems this was introduced in 9902b2315d217190a2e508e2dbad18adcc3aeb29.
and recently caused this problem 849818. 

Do we still need to group by recipeset id for beaker-watchdog?
Comment 1 Nick Coghlan 2012-10-17 04:39:48 UTC 
Bulk reassignment of issues as Bill has moved to another team.
Comment 2 Dan Callaghan 2012-10-25 04:49:45 UTC 
I suspect this is for multi-host tests, so that the external watchdog does not kick in so long as at least one recipe is still alive and working.

Is there any compelling reason why we should change this, apart from bug 849818 which is now fixed?
Comment 3 Raymond Mancy 2012-10-29 00:10:16 UTC 
No, this can be closed
Note You need to log in before you can comment on or make changes to this bug.