Bug 679879 - Issue: testing using key/value for selection of test host is unreliable
Summary: Issue: testing using key/value for selection of test host is unreliable
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: tests
Version: 0.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: Bill Peck
QA Contact:
URL:
Whiteboard:
: 688906 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-23 18:43 UTC by PaulB
Modified: 2019-05-22 13:38 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-07 03:39:34 UTC


Attachments (Terms of Use)

Description PaulB 2011-02-23 18:43:18 UTC
Description of problem:
Running certain tests I need to avoid the selection of a host with specific key/value. However, there is an issue when there are multiple entries for the key/value, as the undersired host can still be chosen.

For instance I need to avoid the selection of a system that has "cciss" key/value. I have tried using both of the following:
------------------------------------------------------------------
<hostRequires>
<and>
 <key_value key="BOOTDISK" op="!=" value="cciss"/>
</and>
</hostRequires>

-and-

<hostRequires>
<and>
 <key_value key="MODULE" op="!=" value="cciss"/>
</and>
</hostRequires>
------------------------------------------------------------------
Issue is when the system has multplie key/vales of BOOTDISK or MODULE,
an undesired system can still be selected.

How reproducible:
See job example in next comment.

Actual results:
System with undesired key/value is selected.

Expected results:
System with undesired key/value omitted.

Additional info:
See next comment for details.

Comment 2 Marian Csontos 2011-02-24 07:50:36 UTC
This is how SQL joins work:
- op="=" -- there exists a node with value equall to the value attribute
- op="!=" -- there exists a node with value not equall to the value attribte

We need a way to request a LEFT OUTER JOINs to specify there is no node (not) matching criteria, e.g.

  <not><key_value .../></not>

Is there a better way?

Comment 3 Bill Peck 2011-03-28 15:47:43 UTC
*** Bug 688906 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.