Bug 1622023 - Bandwidth warnings based on bridge speed that is not actual speed of the bond
Summary: Bandwidth warnings based on bridge speed that is not actual speed of the bond
Keywords:
Status: CLOSED DUPLICATE of bug 1625098
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.2.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.2.7
: ---
Assignee: Edward Haas
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-24 08:00 UTC by Marian Jankular
Modified: 2021-12-10 17:13 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-20 06:21:34 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-44255 0 None None None 2021-12-10 17:13:40 UTC

Description Marian Jankular 2018-08-24 08:00:48 UTC 
Description of problem:
RHV is generating bandwidth warnings based on bridge speed that is not actual (speed is set to 1Gb/s while bond where the bridge is on is 20Gb/s )

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

How reproducible:
always

Steps to Reproduce:
1. create bond that have more that 1Gb/s 
2. as best example put storage vlan on that bond
3. storage bridge will be reported as 1Gb/s 


Actual results:
manager will report bandwidth warnings when the speed will exceed 1Gb/s

Expected results:
manager will report bandwidth warnings when the speed will exceed bond speed

Additional info:
I do not know what would be the best solution for this:

1, not to report bridge by default as 1Gb/s 
2, or to bypass bridge and report underlying physical interface
Comment 1 Dan Kenigsberg 2018-08-29 07:50:53 UTC 
Could you share

  vdsm-client Host getAllStats

as I would like to see what is the speeds reported by Vdsm on bond and network.
Comment 4 Dominik Holler 2018-09-19 09:24:10 UTC 
Is this a duplicate of bug 1625098 ?
Comment 5 Edward Haas 2018-09-20 06:21:34 UTC 

*** This bug has been marked as a duplicate of bug 1625098 ***
Note You need to log in before you can comment on or make changes to this bug.