Bug 1619353 - [UI] Bond slave total values have the wrong unit
Summary: [UI] Bond slave total values have the wrong unit
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.Core
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ovirt-4.2.7
: ---
Assignee: Ales Musil
QA Contact: msheena
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-20 15:10 UTC by Dominik Holler
Modified: 2018-11-02 14:32 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-4.2.7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-02 14:30:21 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)
screeshot (47.91 KB, image/png)
2018-08-20 15:10 UTC, Dominik Holler
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 93833 0 master MERGED webadmin: Fix bond slave statistics constant 2018-08-27 11:54:07 UTC
oVirt gerrit 93946 0 ovirt-engine-4.2 MERGED webadmin: Fix bond slave statistics constant 2018-08-31 08:57:56 UTC

Description Dominik Holler 2018-08-20 15:10:17 UTC
Created attachment 1477274 [details]
screeshot

Description of problem:
In webadmin, the total values have the wrong unit in bond slaves network statistics. In REST-API the unit is correct.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
The unit of "Total Rx" and "Total Tx" of bond slaves is Mbps

Expected results:
The unit of "Total Rx" and "Total Tx" of bond slaves is Bytes

Additional info:

Comment 1 Dan Kenigsberg 2018-08-21 08:37:09 UTC
Any relation to bug 1607175 ?

Comment 2 msheena 2018-09-25 12:26:35 UTC
Verified on:
4.2.7-0.1.el7ev

Comment 3 Sandro Bonazzola 2018-11-02 14:30:21 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.


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