Bug 1029706

Summary:	Need to be able to abort host/guest recipes when their distro trees cannot be satisfied.
Product:	[Retired] Beaker	Reporter:	Raymond Mancy <rmancy>
Component:	scheduler	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.14	CC:	aigao, asaha, dcallagh, ebaak, qwan, rmancy, tools-bugs
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:	2014-08-08 01:54:25 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 Raymond Mancy 2013-11-13 00:23:03 UTC

Description of problem:

Due to BZ#967479, host and guest recipes that cannot be satisfied on the same lab controller may stay queued forever. We need a way of aborting them in a timely fashion.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. submit a host/guest recipeset, where the guest distro tree is not available in any lab where the host's distro tree is.
2. 
3.

Actual results:

It will stay queued forever, or until the distro becomes available in the relevant lab controller.

Expected results:

It should wait for what is a reasonable amount of time (this should be configurable) in the queued state (due to the distro not being available) before it is aborted in the abort_dead_recipes() loop.

Additional info:

Comment 3 Nick Coghlan 2014-08-08 01:54:25 UTC

Fixing bug 967479 seems to generally avoid this problem in practice. Marking this as "WONTFIX" unless/until someone indicates that it is causing a real issue.