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

Bug 1511409

Summary:	[Rest] + [UI] - Report data.current.tx/rx and data.current.tx/rx.bps for bond interfaces and not only for slaves
Product:	[oVirt] ovirt-engine	Reporter:	Michael Burman <mburman>
Component:	BLL.Network	Assignee:	Ales Musil <amusil>
Status:	CLOSED CURRENTRELEASE	QA Contact:	msheena
Severity:	low	Docs Contact:
Priority:	low
Version:	4.2.0	CC:	bugs, mburman
Target Milestone:	ovirt-4.2.7	Flags:	rule-engine: ovirt-4.2+ rule-engine: ovirt-4.3+
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-engine-4.2.7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-02 14:36:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michael Burman 2017-11-09 10:10:48 UTC

Description of problem:
[Rest] + [UI] - Report data.current.tx/rx and data.current.tx/rx.bps for bond interfaces and not only for slaves.

It is seems that we never calculated the current data on top of the bond interfaces, but only it's slaves. 
We should report the current.tx/rx statistics for the bond interface as well.
When sending traffic on top of the bond interface, the current.tx/rx data is reported in rest and ui only for the slave/s, but not for the bond, which remain as:
	
< 1 for tx
< 1 for rx 

Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20171108151837.gita7de53e.el7.centos

How reproducible:
100%

Steps to Reproduce:
1. Send traffic between 2 hosts on top of a bond interface with iperf

Actual results:
data.current.tx/rx and data.current.tx/rx.bps reported in rest and ui only for the bond's slaves, but not for the bond it self. We not calculating the traffic on the bond interface, but only for the slaves.

Expected results:
We should report the current.tx/rx data for the bond interface as well, both in ui and rest api.

Comment 1 Yaniv Kaul 2017-11-12 07:46:51 UTC

Looks like a RFE to me? Are we reporting (not just calculating) the data?

Comment 2 Michael Burman 2017-11-12 11:52:14 UTC

(In reply to Yaniv Kaul from comment #1)
> Looks like a RFE to me? Are we reporting (not just calculating) the data?

No, we don't report this data for bond interfaces at all, only for the slaves.
We do report total tx/rx for bonds, but not the current data. It is always reported as <1

Comment 3 Ales Musil 2018-08-20 09:11:46 UTC

Seems like only the UI is broken. I can see the right speed reported in the REST without any issues.

Comment 4 msheena 2018-09-25 10:12:10 UTC

Verified on:

4.2.7-0.1.el7ev

Both REST and UI.

Comment 5 Sandro Bonazzola 2018-11-02 14:36:54 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.