Created attachment 1379231 [details] Screenshots from Webadmin Description of problem: Under Virtual machines sub-tab, under Templates tab, the listings of the virtual machines that are depended on a template are multiplied by the number of copied of the template disk Version-Release number of selected component (if applicable): rhvm-4.2.1-0.2.el7.noarch How reproducible: Always Steps to Reproduce: 1. Have a template with copies on multiple domains 2. Create a VM from the template 3. Navigate to Templates -> Virtual machines -> the relevant template Actual results: See screenshots Expected results: Listings of VMs, that depend on a template, shouldn't be multiplied by the number of copies of the template Additional info: Screenshots from Webadmin
The underlying issue is the search returning duplicate results. Navigating to VMs and using search to search for Template.name='somename' will result in the same faulty behavior.
More info to follow up on comment 1 - the search mechanism seems to use a join under hood when you supply a condition on a dependent object (instead of, e.g., using the EXISTS operator). For any such object where several objects adhere to a condition, you'll see duplicated results. E.g., see the screen for searching on events.
Created attachment 1380038 [details] Duplicated VMs based on events
Moving to Infra based on comment 2, since this is a general issue with the search.
Created attachment 1386132 [details] Video capture
According to the analysis in the fix, this is a regression introduced by patch a7e724c8686dee8ab03a5f22df17da01170925ca (4.2.0). Marking it as such for visibility.
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Verified in ovirt version 4.2.2.2-0.1.el7. Verified by following the reproducer.
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 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.