Bug 859103

Summary: vdsm: VM disk/cpu stat collection failures flood vdsm.log
Product: Red Hat Enterprise Linux 6 Reporter: Yaniv Kaul <ykaul>
Component: vdsmAssignee: Saveliev Peter <peet>
Status: CLOSED DUPLICATE QA Contact: Haim <hateya>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3CC: abaron, bazulay, iheim, jkt, lpeer, michal.skrivanek, yeylon, ykaul
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-29 14:10:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
vdsm.log none

Description Yaniv Kaul 2012-09-20 14:46:17 UTC 
Description of problem:
[root@gold-vdsd vdsm]# grep -c -E "_getDiskStats|_getCpuStats|getDiskLatency" /var/log/vdsm/vdsm.log
130349
[root@gold-vdsd vdsm]# wc -l /var/log/vdsm/vdsm.log
327082 /var/log/vdsm/vdsm.log

About 1/3 of the log file is flooded with events such as:
Thread-19421::DEBUG::2012-09-20 03:41:05,575::libvirtvm::243::vm.Vm::(_getDiskStats) vmId=`a760141e-2bc0-49d2-81fa-fc58e2a85bd8`::Disk hdc stats not available
Thread-19421::DEBUG::2012-09-20 03:41:05,575::libvirtvm::243::vm.Vm::(_getDiskStats) vmId=`a760141e-2bc0-49d2-81fa-fc58e2a85bd8`::Disk hda stats not available
Thread-19421::DEBUG::2012-09-20 03:41:05,576::libvirtvm::272::vm.Vm::(_getDiskLatency) vmId=`a760141e-2bc0-49d2-81fa-fc58e2a85bd8`::Disk hdc latency not available
Thread-19421::DEBUG::2012-09-20 03:41:05,576::libvirtvm::272::vm.Vm::(_getDiskLatency) vmId=`a760141e-2bc0-49d2-81fa-fc58e2a85bd8`::Disk hda latency not available


Version-Release number of selected component (if applicable):
vdsm-4.9.6-34.0.el6_3.x86_64
libvirt-0.9.10-21.el6_3.4.x86_64

How reproducible:
Not sure. Seen it on several logs.

Steps to Reproduce:
1. Look at vdsm.log - found it on several setups
2.
3.
  
Actual results:


Expected results:


Additional info:

Setting as regression - never seen that in 3.0.
Comment 1 Yaniv Kaul 2012-09-20 14:48:25 UTC 
Created attachment 614946 [details]
vdsm.log
Comment 3 Yaniv Kaul 2012-09-27 20:00:30 UTC 
Dup of https://bugzilla.redhat.com/show_bug.cgi?id=853725 ?
Comment 4 Ayal Baron 2012-09-29 14:10:15 UTC 
(In reply to comment #3)
> Dup of https://bugzilla.redhat.com/show_bug.cgi?id=853725 ?

yes

*** This bug has been marked as a duplicate of bug 853725 ***