Bug 670796

Summary:	bkr should omit tests with excluded architecture
Product:	[Retired] Beaker	Reporter:	Miroslav Vadkerti <mvadkert>
Component:	command line	Assignee:	Bill Peck <bpeck>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	0.7	CC:	bpeck, dcallagh, mcsontos, rmancy
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-01-20 14:44:16 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Miroslav Vadkerti 2011-01-19 12:26:48 UTC

Description of problem:
When creating test xml for beaker using the command below, some of the tests which are excluded for RHEL4 (Releases: -RHEL4) are not omitted:

EXAMPLE:
# bkr workflow-simple --distro=RHEL4-U8 --dryrun --prettyxml --package libuser --debug --arch=x86_64
[snip]
<task name="/CoreOS/libuser/Regression/bz456382-lusermod-not-searching-for-duplicates" role="STANDALONE">
<params/>
</task>
[snip]

When you look at the task, it is correctly excluded for RHEL4:
https://beaker.engineering.redhat.com/tasks/533

Version-Release number of selected component (if applicable):
beaker-client-0.6.1-5.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. Run command in description
  
Actual results:
Task /CoreOS/libuser/Regression/bz456382-lusermod-not-searching-for-duplicates in included in the xml

Expected results:
Task /CoreOS/libuser/Regression/bz456382-lusermod-not-searching-for-duplicates should be excluded from the xml

Additional info:

Comment 1 Dan Callaghan 2011-01-19 22:52:50 UTC

I believe this is expected behaviour. Beaker will drop the task according to its excluded arches/OS versions when the recipe is started, so it does not matter if it appears in the job XML.

The reason bkr client does not exclude it is because it does not fetch task metadata from Beaker server when generating the job XML, so it is not aware of the exclusions.

Comment 2 Miroslav Vadkerti 2011-01-20 07:50:44 UTC

I don't mind if it is included in the xml. After scheduling the xml the recipe is not dropeed. See for example:
https://beaker.engineering.redhat.com/jobs/47378

The reason I need the xml is that I want to add /distribution/reservesys task to the beginning of the job.

Comment 3 Bill Peck 2011-01-20 14:44:16 UTC

When I cloned your job it did drop the task in question.  

The task was updated at  	2011-01-19 12:15:06

And the original job was queued at  	2011-01-19 10:44:00

So I'm guessing the metadata was updated after.