Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1357885 - Update documentation to reflect how to use the like operator in general
Summary: Update documentation to reflect how to use the like operator in general
Status: NEW
Alias: None
Product: Beaker
Classification: Community
Component: scheduler
Version: develop
Hardware: Unspecified
OS: Unspecified
low vote
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2016-07-19 13:24 UTC by Marek Hruscak
Modified: 2019-04-01 14:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:

Attachments (Terms of Use)

Description Marek Hruscak 2016-07-19 13:24:30 UTC
Description of problem:
In I can see <device op="like" description="graphics"/> but it is working. Beaker is unable to use like operator with description column.

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

How reproducible:

Steps to Reproduce:
1. run beaker job with this section in .xml
    <device op="like" description="graphics"/>
    <system_type value="Machine"/>

Actual results:
Beaker do not recognizes this operation

Expected results:
Beaker should use operator like correctly(not as ==), or dokumentation should contains warning about this type of search

Additional info:
Workaround is to append % on the beginning an the end of search string, so it will look like:
    <device op="like" description="%graphics%"/>
    <system_type value="Machine"/>

like is working if I compare in already defined column(type=RAID), like this:
    <key_value key="NR_DISKS" op="&gt;" value="1"/>
    <device op="like" type="RAID" value="egarai"/>
    <system_type value="Machine"/>

Comment 1 Blake McIvor 2016-07-29 05:21:46 UTC
I am leaning towards just updating the documentation to reflect the current behavior due to, how can you be sure on what type of % usage the user requires...

do they want %graphics? %graphics%? graphics%? or is there a way of implementing this that I have not heard of

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