Bug 1510443

Summary: journal spammed with WARN cannot red eth0 speed (when using virtio NICs on the *host*)
Product: [oVirt] vdsm Reporter: Lukas Svaty <lsvaty>
Component: CoreAssignee: Edward Haas <edwardh>
Status: CLOSED CURRENTRELEASE QA Contact: Lucie Leistnerova <lleistne>
Severity: low Docs Contact:
Priority: medium    
Version: 4.20.3CC: bugs, danken, lleistne, michal.skrivanek
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: vdsm-api-4.20.6-62.gitd3023e4.el7.centos.noarch.rpm Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 11:26: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:
Attachments:
Description Flags
vdsmd.log cut off none

Description Lukas Svaty 2017-11-07 12:23:50 UTC
Created attachment 1348932 [details]
vdsmd.log cut off

Description of problem:
$subj every 15 seconds, we can lower that

# tail -f /var/log/vdsm/vdsm.log | grep WARN
2017-11-07 13:19:41,489+0100 WARN  (periodic/1) [root] cannot read eth0 speed (nic:41)
2017-11-07 13:19:56,544+0100 WARN  (periodic/7) [root] cannot read eth0 speed (nic:41)

Adding vdsmd.log, not much I can read from it regarding this issue.

2 questions:
What is causing the warning?
How do we lower the frequency of logging it?

Comment 1 Yaniv Kaul 2017-11-08 07:03:23 UTC
This only happens with virtio NICs, which simply do not advertise their speed.

Comment 2 Edward Haas 2017-11-08 16:21:57 UTC
Changing the logging level to debug. Debug logs should not reach the journal.

Comment 3 Lukas Svaty 2017-11-13 13:20:28 UTC
clean & clean:
# journalctl --unit vdsmd -p 0..4 -S today
# tail -f /var/log/vdsm/vdsm.log | grep WARN

Comment 4 Sandro Bonazzola 2017-12-20 11:26:47 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.