Bug 1136144

Summary:	recipe with <hostRequires force=""/> is dispatched to OpenStack
Product:	[Retired] Beaker	Reporter:	xuezhi ma <xma>
Component:	scheduler	Assignee:	Dan Callaghan <dcallagh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.17	CC:	aigao, asaha, dcallagh, jzhao, rmancy
Target Milestone:	0.18.1	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:	2014-09-12 07:36:26 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 xuezhi ma 2014-09-02 03:18:06 UTC

Description of problem:
I set force in <hostRequires> for testing broken system, but it does not work.

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


How reproducible:
100%

Steps to Reproduce:
1. Choose a broken system.
2. Submit a job with the broken or manual system like
<hostRequires force="$brokensystem"/>
3. Check the job.

Actual results:
Job can *not* run with the broken or manual system.

Expected results:
Job can be run on the broken or manual system


Additional info:

Comment 1 xuezhi ma 2014-09-02 03:28:18 UTC

fore in <hostRequires> work well if I delete my openstack credentials in beaker.

Comment 2 Dan Callaghan 2014-09-02 03:37:49 UTC

So the bug is that <hostRequires force="$FQDN"/> should use $FQDN, but if OpenStack is enabled and the user has supplied credentials then Beaker will send the recipe to OpenStack instead of using the named system.

We are just missing a check for the 'force' attribute in XmlHost.virtualisable().

Comment 3 Dan Callaghan 2014-09-02 03:46:05 UTC

Looks like this has been broken since 0.17 introduced force="".

Comment 4 Dan Callaghan 2014-09-02 03:48:54 UTC

On Gerrit: http://gerrit.beaker-project.org/3304

Comment 5 Dan Callaghan 2014-09-02 08:14:36 UTC

This should probably go into 0.18.1, no reason to rush it into 0.18.

Comment 8 Dan Callaghan 2014-09-12 07:36:26 UTC

Beaker 0.18.1 has been released.