Bug 1270571 - Network tooltip - Improve and correct network tooltip
Summary: Network tooltip - Improve and correct network tooltip
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 3.6.0
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Dan Kenigsberg
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-11 11:17 UTC by Michael Burman
Modified: 2017-12-22 07:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-27 14:22:49 UTC
oVirt Team: Network
ylavi: ovirt-4.0.0?
mburman: planning_ack?
mburman: devel_ack?
mburman: testing_ack?


Attachments (Terms of Use)

Description Michael Burman 2015-10-11 11:17:09 UTC
Description of problem:
Network tooltip - Improve and correct network tooltip.

There are few small corrections to be done on the network's tooltip in setup networks, such:

1) Host Network's configuration differ from DC
'Network's' --> 'network'

2) Align numbers in network tooltip. 
Sometimes numbers aligned to the right, in case of long numbers, they aligned to center(QoS).    

3) QoS Out average link share/real time/upper limit -->
'Out' --> 'out' (middle of sentence). 


Version-Release number of selected component (if applicable):
3.6.0-0.18.el6

Comment 1 Red Hat Bugzilla Rules Engine 2015-10-22 09:09:48 UTC
This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset.
Please set the correct milestone or add the z-stream flag.

Comment 2 Yaniv Lavi 2015-10-29 12:39:15 UTC
In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone.

Comment 4 Dan Kenigsberg 2016-03-27 14:22:49 UTC
Annoying glitches, but now the elevi is gone, I do not see them fixed anytime soon.


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