Bug 1496329 - [UI] - CPU QoS is not reachable and has cut-off in the end of the page
Summary: [UI] - CPU QoS is not reachable and has cut-off in the end of the page
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ovirt-4.2.0
: ---
Assignee: Alexander Wels
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-27 05:42 UTC by Michael Burman
Modified: 2017-12-20 11:45 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:45:25 UTC
oVirt Team: UX
Embargoed:
rule-engine: ovirt-4.2+

Attachments (Terms of Use)
record1 (2.51 MB, application/x-gzip)
2017-09-27 05:42 UTC, Michael Burman 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 82318 0 master MERGED webadmin: DC QoS fixes 2017-09-28 11:55:01 UTC

Description Michael Burman 2017-09-27 05:42:31 UTC 
Created attachment 1331313 [details]
record1

Description of problem:
[UI] - CPU QoS is not reachable and has cut-off in the end of the page.

The CPU QoS entities are not available because the page has a cut-off in the end of the page and we can't scroll down any more.

Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20170926175518.git0d20200.el7.centos

How reproducible:
100%

Steps to Reproduce:
1. Go to DC > QoS > create CPU QoS entity
2. Try to reach it, edit it or remove it

Actual results:
CPU QoS entity is not available
Comment 1 Lucie Leistnerova 2017-11-21 13:02:15 UTC 
CPU QoS are all visible

verified in ovirt-engine-4.2.0-0.5.master.el7.noarch
Comment 2 Sandro Bonazzola 2017-12-20 11:45:25 UTC 
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, 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.