Bug 1005865

Summary:	Don't check if beah is available for distro when alternative harness is used
Product:	[Retired] Beaker	Reporter:	Ľuboš Kardoš <lkardos>
Component:	scheduler	Assignee:	Amit Saha <asaha>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.14	CC:	aigao, asaha, dcallagh, ebaak, jorton, mganisin, qwan, rmancy, tools-bugs, xjia
Target Milestone:	0.16.1	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-26 23:54:24 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:

Comment 2 Dan Callaghan 2013-09-16 11:17:08 UTC

The reason Beaker checks to make sure the harness repo exists is because Anaconda will complain if we define a repo in the kickstart which is unreachable.

But if the recipe is using an alternate harness Beaker could just skip the harness repo definition, instead of complaining.

Comment 3 Nick Coghlan 2013-11-05 01:56:58 UTC

I guess if any alternative harnesses are depending on libraries we currently have in the default harness repos, they should really be providing their own copies rather than relying on the fact beah also needs them.

So +1 for skipping the harnessrepo configuration when the chosen harness is anything other than beah.

Comment 4 Amit Saha 2014-03-14 03:48:10 UTC

http://gerrit.beaker-project.org/#/c/2916/

Comment 5 Amit Saha 2014-03-19 03:26:11 UTC

Getting this into 0.16.1 instead: http://gerrit.beaker-project.org/#/c/2935/

Comment 8 Dan Callaghan 2014-03-26 23:54:24 UTC

Beaker 0.16.1 has been released.