Bug 1064489

Summary: do not report negative rx/tx rate when Linux counters wrap
Product: [Retired] oVirt Reporter: Dan Kenigsberg <danken>
Component: vdsmAssignee: Dan Kenigsberg <danken>
Status: CLOSED NEXTRELEASE QA Contact: Meni Yakove <myakove>
Severity: high Docs Contact:
Priority: high    
Version: 3.4CC: acathrow, audgiri, bazulay, danken, emesika, gchakkar, gklein, iheim, lpeer, mgoldboi, mkalinin, ngupta, Rhev-m-bugs, sradco, tdosek, ybronhei, yeylon, ylavi
Target Milestone: ---Keywords: Triaged
Target Release: 3.3.5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1062166 Environment:
Last Closed: 2014-03-31 12:23:18 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:
Bug Depends On: 1062166    
Bug Blocks: 1047459    

Description Dan Kenigsberg 2014-02-12 17:20:49 UTC 
+++ This bug was initially created as a clone of Bug #1062166 +++

+++ This bug was initially created as a clone of Bug #1047459 +++

When /sys/class/net/vnet0/statistics/tx_bytes reaches its 32 bit maximum value, it wraps back to 0. Vdsm must take this into account when calculating the txRate of vnics. Otherwise, a negative value may pollute the data warehouse.
Comment 1 Dan Kenigsberg 2014-03-31 12:23:18 UTC 
It's safe enough to verify only the 3.4 clone of this bug (bug 1062166).
Comment 2 Shirly Radco 2014-07-03 08:47:36 UTC 
*** Bug 1115596 has been marked as a duplicate of this bug. ***