Created attachment 1647601 [details] screenshot Description of problem: Via web-admin, user can't see attached cluster to a DC through the cluster tab under a specific DC. Instead, an infinite 'progress bar' is shown. Version-Release number of selected component (if applicable): 4.4.0-0.13.master.el7 How reproducible: 100% Steps to Reproduce: 1.Go to <data center name> 2.Press on the cluster tab Actual results: Attached DC clusters not shown. Expected results: Attached DC clusters should be shown. If none clusters attached exist, appropriate note should be shown. Additional info: screenshot attached
After reverting https://gerrit.ovirt.org/c/105196/ the list is shown and does not hang on loading.
this bug has been fixed by Dominik Holler https://gerrit.ovirt.org/c/106181/ there's another issue in the search as Dominik mentioned in the email thread for example when using REST-API: GET http://localhost:8080/ovirt-engine/api/clusters?search=datacenter.name=Default engine log produces: 2020-01-08 15:51:33,434+01 INFO [org.ovirt.engine.core.bll.SearchQuery] (default task-17) [09acad16-a073-409a-9cc6-48a78ef64624] ResourceManager::searchBusinessObjects - erroneous search text - ''clusters: datacenter.name=Default'' error - ''clusters: datacenter$n$ame=Default''
A bug has been opened regarding the Search Bug mentioned in Comment (By Eli) https://bugzilla.redhat.com/show_bug.cgi?id=1789262
This bug is targeted to 4.4.3 and in modified state. can we re-target to 4.4.0 and move to QA?
Bug verified via web-admin. Correct attached clusters is shown in appropriate time and all logs are clean as expected. worked on: rhvm-4.4.0-0.29.master.el8ev.noarch vdsm-jsonrpc-java-1.5.4-1.el8ev.noarch qemu-kvm-4.2.0-16.module+el8.2.0+6092+4f2391c1.x86_64 libvirt-client-6.0.0-15.module+el8.2.0+6106+b6345808.x86_64
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.