Ameya as mentioned in upstream bug you need to use 'name' identifier when searching for VMs which name starts with predefined keyword: https://bugzilla.redhat.com/show_bug.cgi?id=1431882#c10 In your example: Vms: name=osp* Above should work and return all VMs with name starting with 'osp' prefix. But below will not work: Vms: osp* Vms: osp and both will always return empty list because 'os' is predefined keyword. You can find list of all existing predefined keywords in https://bugzilla.redhat.com/show_bug.cgi?id=1431882#c8 Could you please confirm with customer that search using 'name' identifier works as expected?
I'm the customer. It doesn't work as expected. Expected is to search for Vms: osw and find hosts that contain the string osw.
(In reply to Logan Kuhn from comment #3) > I'm the customer. It doesn't work as expected. Expected is to search for > Vms: osw and find hosts that contain the string osw. So could you please use the full name format: Vms: name=osw*
Yes that works, but it's not the slightest bit intuitive and presents like a bug in the interface. If an administrator is evaluating ovirt or rhev for production use, types in the name of a system starting with a keyword (Vms: osw) and finds zero results even though the guest exists, what impression is that going to give them? It's the first thing someone is going to do and it doesn't work. I can understand the amount of work it'd take to rewrite a search interface and I don't envy the task. However, could there be something to make it more intuitive? for example Vms: osw has a pop up that says "Did you mean: Vms: name=osw?" With a link to the corresponding documentation explaining the convenience of using keywords. It'd be a simply little pop up and that capability is already integrated into the product with Patternfly.
Hello, i would also vote for at least a pop-up as we have the exact same issue and most of my colleagues are used to just typing 'foo' in the search bar and they get a list of all servers starting with foo. Now with osp this changes and they should at least get a pop-up saying did u mean name=osp* .
Thank you for all the hardwork that went into this.
Steps: 1) Create an instance (VM, disk,...) that starts with special keyword (id, os, vm_names,...), for example VM 'idempiere' 2) Search for that instance: a) using only the keyword (Vms: id) - nothing is returned b) keyword + any characters (Vms: id*) - correct VM is returned c) keyword + additional characters from the instance's name (Vms: idem) - correct VM is returned d) using attribute with only keyword (Vms: name=id) - nothing is returned e) using attribute with keyword + any characters (Vms: name=id*) - correct VM is returned Results: Search engine is behaving correctly limited only by the sole keywords. Verified in: ovirt-engine-4.4.3.5-0.5.el8ev.noarch
Thank you!!! Any chance this could get back ported to 4.3? I ask because my company isn't upgrading to 4.4 until next year.
(In reply to Logan Kuhn from comment #16) > Thank you!!! > > Any chance this could get back ported to 4.3? I ask because my company > isn't upgrading to 4.4 until next year. No, RHV 4.3.11 has already been released and it was the last RHV Manager 4.3.z release.
Hi Eli, please review this doc text for the errata: With this enhancement, you can now perform a free text search in the Administration Portal that includes internally defined keywords.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Low: Red Hat Virtualization security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5179
(In reply to Eli Marcus from comment #18) > Hi Eli, > please review this doc text for the errata: > > With this enhancement, you can now perform a free text search in the > Administration Portal that includes internally defined keywords. "that includes" => "that starts with"