Description of problem: VmStats - Error in vdsm.log for (_getRunningVmStats) --> KeyError: 'block.0.rd.bytes' from time to time There is an error in vdsm log while trying to collect running VMs stats - - Thread-19808::ERROR::2015-11-11 08:24:02,400::vm::1390::virt.vm::(_getRunningVmStats) vmId=`0d211260-2c0b-4626-a438-4fc8fc8c76a3`::Error fetching vm stats Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 1387, in _getRunningVmStats vm_sample.interval) File "/usr/share/vdsm/virt/vmstats.py", line 43, in produce disks(vm, stats, first_sample, last_sample, interval) File "/usr/share/vdsm/virt/vmstats.py", line 262, in disks interval)) File "/usr/share/vdsm/virt/vmstats.py", line 292, in _disk_rate first_sample['block.%d.rd.bytes' % first_index]) KeyError: 'block.0.rd.bytes' - I'm not sure what invoking this or what the reason for this error. I have 1 running on this server for 8 days and this error appears in vdsm log from time to time. Version-Release number of selected component (if applicable): 3.6.0.3-0.1.el6 vdsm-4.17.10.1-0.el7ev.noarch libvirt-1.2.17-13.el7.x86_64 qemu-kvm-common-rhev-2.3.0-31.el7.x86_64
Created attachment 1093143 [details] Logs
(In reply to Michael Burman from comment #0) > Description of problem: > VmStats - Error in vdsm.log for (_getRunningVmStats) --> KeyError: > 'block.0.rd.bytes' from time to time > > There is an error in vdsm log while trying to collect running VMs stats - > > - Thread-19808::ERROR::2015-11-11 > 08:24:02,400::vm::1390::virt.vm::(_getRunningVmStats) > vmId=`0d211260-2c0b-4626-a438-4fc8fc8c76a3`::Error fetching vm stats > Traceback (most recent call last): > File "/usr/share/vdsm/virt/vm.py", line 1387, in _getRunningVmStats > vm_sample.interval) > File "/usr/share/vdsm/virt/vmstats.py", line 43, in produce > disks(vm, stats, first_sample, last_sample, interval) > File "/usr/share/vdsm/virt/vmstats.py", line 262, in disks > interval)) > File "/usr/share/vdsm/virt/vmstats.py", line 292, in _disk_rate > first_sample['block.%d.rd.bytes' % first_index]) > KeyError: 'block.0.rd.bytes' > > - I'm not sure what invoking this or what the reason for this error. > I have 1 running on this server for 8 days and this error appears in vdsm > log from time to time. > > Version-Release number of selected component (if applicable): > 3.6.0.3-0.1.el6 > vdsm-4.17.10.1-0.el7ev.noarch > libvirt-1.2.17-13.el7.x86_64 > qemu-kvm-common-rhev-2.3.0-31.el7.x86_64 Looking at the logs, this happened when storage is unresponsive, which is a bigger problem per se. Nevertheless, VDSM should handle missing block stats. Working on a patch.
This is about noise in the logs - doesn't affect customers flow at all
patch posted -> POST
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
Verified on - vdsm-4.17.21-0.el7ev.noarch 3.6.3.2-0.1.el6