Bug 1625098

Summary: Wrong network threshold limit warnings on vdsm version 4.20.35-1.el7
Product: [oVirt] vdsm Reporter: support_it_at
Component: GeneralAssignee: Edward Haas <edwardh>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.20.31CC: bugs, edwardh, gveitmic, jbainbri, kirill.prokin, kmashalk, mburman, mjankula
Target Milestone: ovirt-4.2.7Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: v4.20.40 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-02 14:29:47 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 support_it_at 2018-09-04 06:30:08 UTC
Description of problem:
Different speed reported for network vlan interface between  /sys/class/net/*/speed and vdsm-client Host getStats

-> oVirt Engine raises a warning when network threshold is over 100%, although 10 Gbit link is only utilized over 1 Gbit.


Version-Release number of selected component (if applicable):
oVirt                   4.2.5
vdsm.x86_64             4.20.35-1.el7
vdsm-common.noarch      4.20.35-1.el7
ovirt-release42.noarch  4.2.5.1-1.el7


How reproducible:
Vlan interface on a 10 Gbit link and utilization is over 1 Gbit
100 % reproducable


Steps to Reproduce:
1. 10 Gbit network card
2. 1 or several VLANs on it
3. Copy data over VLAN with over 120 MB/s

Actual results:
In Engine:
Warning: Host xxx has network interface which exceeded the defined threshold [95%] (enp10s0.100: transmit rate[1%], receive rate [100%])


Expected results:
No warning raised


Additional info:
Example:
cat /sys/class/net/enp9s0/speed
10000

cat /sys/class/net/enp9s0.80/speed
10000

cat /sys/class/net/vm-int-nfs/speed
cat: /sys/class/net/vm-int-nfs/speed: Invalid argument     <- this is the bridge for the VMs

vdsm-client Host getStats ->
...
        "enp9s0": {
            "rxErrors": "0", 
            "name": "enp9s0", 
            "tx": "3335325754762", 
            "txDropped": "0", 
            "sampleTime": 1535970960.602359, 
            "rx": "5916567956502", 
            "txErrors": "0", 
            "state": "up", 
            "speed": "10000", 
            "rxDropped": "0"
        }, 
...
        "enp9s0.80": {
            "rxErrors": "0", 
            "name": "enp9s0.80", 
            "tx": "3180024039398", 
            "txDropped": "0", 
            "sampleTime": 1535970960.602359, 
            "rx": "5669421065686", 
            "txErrors": "0", 
            "state": "up", 
            "speed": "1000", 
            "rxDropped": "0"
        }, 
...
        "vm-int-nfs": {
            "rxErrors": "0", 
            "name": "vm-int-nfs", 
            "tx": "508", 
            "txDropped": "0", 
            "sampleTime": 1535970960.602359, 
            "rx": "4428568", 
            "txErrors": "0", 
            "state": "up", 
            "speed": "1000", 
            "rxDropped": "0"
        }, 
...

Comment 1 Michael Burman 2018-09-18 09:59:57 UTC
Verified upstream with - vdsm-4.20.39-15.gitae7d021.el7 and 4.2.6.5-0.0.master.20180916153857.git759b52e.el7

Comment 2 Raz Tamir 2018-09-18 10:30:08 UTC
QE verification bot: the bug was verified upstream

Comment 3 Edward Haas 2018-09-20 06:21:34 UTC
*** Bug 1622023 has been marked as a duplicate of this bug. ***

Comment 4 Dan Kenigsberg 2018-09-30 12:22:30 UTC
*** Bug 1600744 has been marked as a duplicate of this bug. ***

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