Bug 722367

Summary:	absent harness repos are silently ignored
Product:	[Retired] Beaker	Reporter:	Raymond Mancy <rmancy>
Component:	scheduler	Assignee:	Raymond Mancy <rmancy>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.6	CC:	bpeck, dcallagh, ebaak, 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:	2011-08-12 02:43:53 UTC	Type:	---
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 2011-07-15 03:03:13 UTC

If a server has no harness repos, the running of the job still continues.

I think we should abort the job if we come across this scenario.

Comment 1 Bill Peck 2011-07-15 13:13:49 UTC

What if all the stars align and we end up with the harness in the distro?

Comment 2 Raymond Mancy 2011-07-17 21:57:32 UTC

You mean in the main distro repo...?

If we're putting harness repo details in the ks at schedule time and we notice that it's broken, I don't think we should assume it will fix itself.