Description of problem: Vms do not appear in 'virtual machine' main tab if host is selected in RHEV-M side pane. screen shows empty (0 item) despite there are large number of vms running on the host. Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization 3.3 How reproducible: Always Steps to Reproduce: 1. Expand the side pan and select a host in a cluster. 2. click on 'virtual machine' tab main tab. Actual results: No vms listed Expected results: Should list all the running virtual machines. I have tested this on RHEV 3.2 and it works properly. Additional info: 1) I see below warning message in engine.log file upon clicking the virtual machine when a host is selected in side pane: 2014-02-11 17:57:12,725 WARN [org.ovirt.engine.core.bll.SearchQuery] (ajp-/127.0.0.1:8702-11) ResourceManager::searchBusinessObjects - erroneous search text - Vms: Hosts.name = rhev1 2) issue screenshot attached.
Yes, its not working on upstream as well.
Eli, There is a fix for the UI, http://gerrit.ovirt.org/#/c/24899/ its Fix this bug but we may have another issue in the Search infrastructure.
*** Bug 1068478 has been marked as a duplicate of this bug. ***
Hi Shahar, The patch http://gerrit.ovirt.org/#/c/24899/ seems to be the right way to fix the issue described in this bug. Can you explain what other issue you have as stated in commend #6.
The reasons is that other tabs use the following: prefix.argvalue = "Storage: host.name =" prefix.argvalue = "Template: Hosts.name =" Vms was written like that as well, ie the ability to enumerate running VMs via hosts properties. Again I am not sure that it is needed for Vms but it does like it do.
Should we push the UI patch as well? http://gerrit.ovirt.org/#/c/24899/
(In reply to Shahar Havivi from comment #10) > Should we push the UI patch as well? > http://gerrit.ovirt.org/#/c/24899/ No we don't need the UI patch, the backend patch takes care of it
Yes it is fixed, merged to 3.4 on Feb 25th. Moving to modified
ok, av2.
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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0506.html