Created attachment 1243638 [details]
Description of problem:
according to :
The search should have Hosts.hosts-prop (The hosts-prop can be for example name/status/template and more)
when typing in the search :"Hosts=..", there is autocomplete for 'hosts' but then the 's' immediately paints in red, and there is no option to complete the search
Version-Release number of selected component (if applicable):
Red Hat Virtualization Manager Version: 22.214.171.124-0.1.el7ev
Steps to Reproduce:
1. go to vms tab in webadmin portal
2. try to perform this search = "VMs: Hosts.name="*"
you left VMs: at the beginning, so you're searching in context of VM object.
> 2. try to perform this search = "VMs: Hosts.name="*"
I do not see the documentation saying that it is supported. It is not
When typing Hosts. (in Virtual machines) I should get auto complete options , as same as Templates gives the options- name, comment, os and more
Created attachment 1316587 [details]
you still have Vms: up front. "Hosts:" is no a property of the VM
Created attachment 1316591 [details]
please see the documentation
not sure it's supposed to work, Martin?
Seems like a bug (regression ...)
After investigating the bug , this is not a regressions , it never worked ...
The problem was that from VMs search you can not search for Hosts
attributes (i.e. "Vms:Hosts.<some attribute>"
The reason for that is that both "Hosts" and "host" are available as
search parameters. The search engine is case insensitive and therefor
since it is processing the search string character-by-character after
analysing the entity type (i.e what appears as "<entity>:" , "vms:" for
example) it get the "host" as a token when you are writing "Hosts" and
marks the "s" at the end of the "Hosts" string as an error.
Moving to 4.2 as this never worked (although it's documented) and search backend is very fragile part of the code
autocomplete on 'Vms: Hosts.' works fine and search also (the same for 'Vms: host.*')
verified in ovirt-engine-4.2.0-0.0.master.20171009063348.gitf2b70a1.el7.centos.noarch
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.
Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.