Bug 1513580 - Searching for VM called 'memory' broken
Summary: Searching for VM called 'memory' broken
Keywords:
Status: CLOSED DUPLICATE of bug 1431882
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: future
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Martin Perina
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-15 16:02 UTC by jniederm
Modified: 2017-11-15 20:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-15 20:17:10 UTC
oVirt Team: Infra
Embargoed:


Attachments (Terms of Use)
screenshot.png (28.85 KB, image/png)
2017-11-15 16:02 UTC, jniederm
no flags Details

Description jniederm 2017-11-15 16:02:33 UTC
Created attachment 1352711 [details]
screenshot.png

Description of problem:
A VM called 'memory' can't be found using webadmin search bar. However search results for any prefix of its name ('m', 'me', ...) contains the VM.

Version-Release number of selected component (if applicable):
current master, commit 9e4a40da1a

How reproducible:
100%

Steps to Reproduce:
1. Create a VM called 'memory'
2. I webadmin, VMs tab select search bar labeled 'Vms:'
3. Enter 'memory' and confirm

Actual results:
VM called 'memory' is not part of search results

Expected results:
VM called 'memory' is part of search results


Additional info:
Each search generates engine log warning like:
2017-11-15 16:50:08,987+01 WARN  [org.ovirt.engine.core.bll.SearchQuery] (default task-67) [6823b13c-73d9-4c26-929a-8e847352afcd] ResourceManager::searchBusinessObjects - Invalid search text - ''Vms:memory''

Comment 1 Martin Perina 2017-11-15 20:16:36 UTC
'memory' is a reserved word and its parsing has higher priority, see [1]. If you want to search VMs which name starts with reserved word you need to use following pattern:

  Vms: name=memory


[1] https://bugzilla.redhat.com/show_bug.cgi?id=1431882#c8

Comment 2 Martin Perina 2017-11-15 20:17:10 UTC

*** This bug has been marked as a duplicate of bug 1431882 ***


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