Bug 885554 - beakerd aborts recipes which have no systems, even if they could be satisfied by oVirt/RHEV
Summary: beakerd aborts recipes which have no systems, even if they could be satisfied...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: 0.10
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: 0.11
Assignee: Dan Callaghan
QA Contact: Raymond Mancy
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-10 03:48 UTC by Dan Callaghan
Modified: 2018-02-06 00:41 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-17 04:33:19 UTC
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.