Bug 885554

Summary: beakerd aborts recipes which have no systems, even if they could be satisfied by oVirt/RHEV
Product: [Retired] Beaker Reporter: Dan Callaghan <dcallagh>
Component: schedulerAssignee: Dan Callaghan <dcallagh>
Status: CLOSED CURRENTRELEASE QA Contact: Raymond Mancy <rmancy>
Severity: unspecified Docs Contact:
Priority: low    
Version: 0.10CC: asaha, dcallagh, ebaak, mishin, qwan, rglasz, rmancy
Target Milestone: 0.11   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-17 04:33:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dan Callaghan 2012-12-10 03:48:05 UTC 
beakerd has some logic for aborting recipes if they have no candidate systems (in new_recipes and also in dead_recipes). Now that we have oVirt/RHEV support, it's perfectly legitimate for a recipe to have no physical candidate systems but still be runnable. The logic needs to be extended to check that either oVirt integration is disabled or the recipe cannot be run on oVirt.
Comment 1 Dan Callaghan 2012-12-10 04:09:18 UTC 
On Gerrit: http://gerrit.beaker-project.org/1545
Comment 5 Dan Callaghan 2013-01-17 04:33:19 UTC 
Beaker 0.11.0 has been released.