Bug 690035 - Dead recipe removal is not triggered when distro remains in some labs
Summary: Dead recipe removal is not triggered when distro remains in some labs
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: 0.6
Hardware: Unspecified
OS: Unspecified
low
low vote
Target Milestone: ---
Assignee: Dan Callaghan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-23 04:51 UTC by Dan Callaghan
Modified: 2012-09-05 03:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-05 03:23:55 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Dan Callaghan 2011-03-23 04:51:51 UTC 
As per bug 668473, the scheduler includes a dead_recipes routine which checks for queued recipes which can never proceed because their requirements can no longer be satisfied.

Right now, it only looks for recipes whose distro has been completely expired from all labs. But if the recipe has <hostRequires/> which need a specific lab, and the distro has been expired from *that particular lab* (but not from all), it is not picked up by the dead_recipes routine even though the recipe will never be scheduled.
Comment 1 Dan Callaghan 2012-09-04 22:43:10 UTC 
It is not trivial to determine whether a given <hostRequires/> limits the recipe to a particular lab. There are also indirect limitations, such as if the <hostRequires/> effectively limits the recipe to systems which are in labs where the distro is not present.

We also have this outstanding problem of how Beaker can determine whether a distro tree is missing because it's been deleted, or hasn't been synced yet.

So I will need to think about a good way to solve this...
Comment 2 Dan Callaghan 2012-09-05 03:23:55 UTC 
Closing as WONTFIX since solving this problem is not really feasible.

A better solution is to make sure distros are deleted from all labs promptly when they expire: bug 717424.
Note You need to log in before you can comment on or make changes to this bug.