Created attachment 1437845 [details] vdsm log Description of problem: KeyError: 'rx' on VM shutdown On each VM shutdown, this error appears in vdsm log: 2018-05-17 12:05:21,572+0300 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmIoTunePolicies succeeded in 0.00 seconds (__init__:573) 2018-05-17 12:05:22,806+0300 WARN (periodic/1) [virt.vmstats] Missing stat: 'net.0.rx.errs' for vm 5cdbe981-039c-44cf-95cd-84081e5bd688 (vmstats:564) 2018-05-17 12:05:22,806+0300 WARN (periodic/1) [virt.vmstats] Missing stat: 'net.0.rx.bytes' for vm 5cdbe981-039c-44cf-95cd-84081e5bd688 (vmstats:564) 2018-05-17 12:05:22,807+0300 ERROR (periodic/1) [virt.vmstats] VM metrics collection failed (vmstats:265) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vmstats.py", line 249, in send_metrics data[netprefix + '.rx_bytes'] = if_info['rx'] KeyError: 'rx' 2018-05-17 12:05:22,807+0300 INFO (periodic/1) [Executor] Worker was discarded (executor:305) Version-Release number of selected component (if applicable): vdsm-4.20.27.1-1.el7ev.x86_64 How reproducible: 100% Steps to Reproduce: 1. Start VM on latest 4.2 2. Shut down VM Actual results: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vmstats.py", line 249, in send_metrics data[netprefix + '.rx_bytes'] = if_info['rx'] KeyError: 'rx' Expected results: No errors in vdsm log on VM shut down
There are several duplicate reports like this. All these will be solved by https://gerrit.ovirt.org/#/c/91354/
Verified on: 4.2.8.1-0.1.el7ev
Yes, my mistake, I checked it on 4.3, Verification on: ovirt-engine-4.3.0-0.4.master.20181230173049.gitef04cb4.el7.noarch vdsm-4.30.4-81.gitad6147e.el7.x86_64 libvirt-client-4.5.0-10.el7_6.3.x86_64 qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.0 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.