| Summary: | Dead recipe removal is not triggered when distro remains in some labs | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Dan Callaghan <dcallagh> |
| Component: | scheduler | Assignee: | Dan Callaghan <dcallagh> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| 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: | 2012-09-05 03:23:55 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
Dan Callaghan
2011-03-23 04:51:51 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... 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. |