Bug 1558539

Summary: activating a tag takes too long, shows tall empty VM grid
Product: [oVirt] ovirt-engine Reporter: Greg Sheremeta <gshereme>
Component: Frontend.WebAdminAssignee: Alexander Wels <awels>
Status: CLOSED CURRENTRELEASE QA Contact: samuel macko <smacko>
Severity: low Docs Contact:
Priority: low    
Version: 4.2.1CC: bugs, lsvaty
Target Milestone: ovirt-4.3.0Flags: rule-engine: ovirt-4.3+
dnecpal: testing_plan_complete-
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.0_alpha Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-13 16:37:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: UX RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
activate tag -- slowness bug
none
screenshot none

Description Greg Sheremeta 2018-03-20 12:45:28 UTC 
Created attachment 1410446 [details]
activate tag -- slowness bug

Description of problem:
activating a tag takes too long, shows tall empty VM grid

Version-Release number of selected component (if applicable):
4.2.1

How reproducible:
?
got this from a video Moran made

Steps to Reproduce:
see attachment
Comment 1 Greg Sheremeta 2018-03-20 12:47:07 UTC 
Alexander, the query itself is probably too slow, so maybe infra / Eli can work on that. But also the UI should be improved:
1. the grid shouldn't start out that tall
2. there should be a spinner
Comment 2 Greg Sheremeta 2018-03-20 12:47:41 UTC 
Created attachment 1410447 [details]
screenshot
Comment 3 samuel macko 2019-03-04 12:24:02 UTC 
Verified on ovirt-engine-4.3.0.4-0.1.el7.noarch.
Comment 4 Sandro Bonazzola 2019-03-13 16:37:44 UTC 
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.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.