Bug 1157348

Summary:	Job specified to run in container should not check for harness repos
Product:	[Retired] Beaker	Reporter:	Amit Saha <asaha>
Component:	scheduler	Assignee:	Amit Saha <asaha>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.18	CC:	aigao, asaha, dcallagh, dowang, ebaak, linwang
Target Milestone:	19.2	Keywords:	Patch
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-20 03:18:39 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 Amit Saha 2014-10-27 05:11:42 UTC

Description of problem:

When using the default harness for jobs running in a container (on Atomic for e.g.), the harness repo should not be checked and the job not aborted.

The check doesn't really make sense since we currently do the check for the harness repo corresponding to the base distro which is most likely different from the distro running in the container.

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

0.18.4

How reproducible:

Always

Steps to Reproduce:
1. Provision a beaker job on an Atomic host with *no* harness ksmeta
2. 
3.

Actual results:

Job aborted

Expected results:


Additional info:


A simple workaround is to specify harness="beah" or harness="restraint" in the ksmeta.

Comment 1 Amit Saha 2014-12-22 06:34:26 UTC

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

Comment 4 Dan Callaghan 2015-01-20 03:18:39 UTC

Beaker 19.2 has been released.