Bug 1636767 - [UI] - VM - Snapshots sub tab - Network Interfaces - Align (Mbps)/(Pkts) to the text
Summary: [UI] - VM - Snapshots sub tab - Network Interfaces - Align (Mbps)/(Pkts) to t...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.2.6.2
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ovirt-4.3.0
: 4.3.0
Assignee: Ales Musil
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-07 14:05 UTC by Michael Burman
Modified: 2019-02-13 07:48 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-4.3.0_alpha
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-13 07:48:02 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.3+
dholler: devel_ack+

Attachments (Terms of Use)
screenshot (21.14 KB, image/png)
2018-10-07 14:05 UTC, Michael Burman 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 94887 0 master MERGED webadmin: Fix align of the "Mbps/Pkts" in snapshot interfaces 2018-10-12 16:51:05 UTC

Description Michael Burman 2018-10-07 14:05:59 UTC 
Created attachment 1491337 [details]
screenshot

Description of problem:
[UI] - VM - Snapshots sub tab - Network Interfaces - Align (Mbps)/(Pkts) to the text

The (Mbps)/(Pkts) snapshot's network interfaces statistics should be aligned to the bold text, just like we did(Ales did) in the VM's network interface. 

Version-Release number of selected component (if applicable):
4.2.7.3-0.0.master.20181007094930.git02c1da0.el7

How reproducible:
100%
Comment 1 Red Hat Bugzilla Rules Engine 2018-10-10 08:10:36 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 2 Michael Burman 2018-10-22 06:59:22 UTC 
Verified on - 4.3.0-0.0.master.20181016132820.gite60d148.el7
Comment 3 Sandro Bonazzola 2018-11-02 14:29:09 UTC 
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.7 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.
Comment 4 Sandro Bonazzola 2018-11-02 14:42:01 UTC 
Closed by mistake, moving back to qa -> verified
Comment 5 Sandro Bonazzola 2019-02-13 07:48:02 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.