Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1496329

Summary: [UI] - CPU QoS is not reachable and has cut-off in the end of the page
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: Frontend.WebAdminAssignee: Alexander Wels <awels>
Status: CLOSED CURRENTRELEASE QA Contact: Lucie Leistnerova <lleistne>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: bugs, gshereme, lleistne, lsvaty, oourfali
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 11:45:25 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
record1 none

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.