Bug 1558539 - activating a tag takes too long, shows tall empty VM grid
Summary: activating a tag takes too long, shows tall empty VM grid
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ovirt-4.3.0
: 4.3.0
Assignee: Alexander Wels
QA Contact: samuel macko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-20 12:45 UTC by Greg Sheremeta
Modified: 2019-03-13 16:37 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-4.3.0_alpha
Clone Of:
Environment:
Last Closed: 2019-03-13 16:37:44 UTC
oVirt Team: UX
Embargoed:
rule-engine: ovirt-4.3+
dnecpal: testing_plan_complete-


Attachments (Terms of Use)
activate tag -- slowness bug (2.84 MB, application/octet-stream)
2018-03-20 12:45 UTC, Greg Sheremeta
no flags Details
screenshot (173.70 KB, image/png)
2018-03-20 12:47 UTC, Greg Sheremeta
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 89326 0 master MERGED webadmin: refresh grid on overlay close 2018-03-22 12:12:46 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.