Bug 1296529

Summary: VM cpu/mem/net usage text is overlapping graph
Product: [oVirt] ovirt-engine Reporter: Pavel Stehlik <pstehlik>
Component: Frontend.WebAdminAssignee: jniederm
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Novotny <pnovotny>
Severity: low Docs Contact:
Priority: medium    
Version: 3.6.0CC: agkesos, bugs, gklein, michal.skrivanek, pstehlik
Target Milestone: ovirt-4.0.0-betaFlags: rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
rule-engine: devel_ack+
pstehlik: testing_ack+
Target Release: 4.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 10:11:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1298089    
Attachments:
Description Flags
vm-graphs-usage none

Description Pavel Stehlik 2016-01-07 12:57:26 UTC
Created attachment 1112438 [details]
vm-graphs-usage

Description of problem:
 Some numbers are overlapping graphical VM usage. See att pic. I'd like to propose to put some more space between graph & numeric value.

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

How reproducible:
100% with FF (43, 40)

Steps to Reproduce:
1. install 3.6 agent into VM and put some load into VMs
2.
3.

Actual results:
some numbers (4..,5..,2..) are covering graph (and vice versa)

Expected results:
more space between graph & value

Additional info:

Comment 1 Michal Skrivanek 2016-01-15 11:30:27 UTC
*** Bug 1298089 has been marked as a duplicate of this bug. ***

Comment 2 Yaniv Kaul 2016-03-13 15:26:31 UTC
Does changing the zoom level of the browser help?

Comment 3 Pavel Stehlik 2016-03-14 10:02:33 UTC
(In reply to Yaniv Kaul from comment #2)
> Does changing the zoom level of the browser help?

No, unfortunately it doesn't.

Comment 5 Sandro Bonazzola 2016-05-02 09:51:18 UTC
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.

Comment 6 Gil Klein 2016-07-27 10:11:56 UTC
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA