Bug 1112998 - Adding new disk to active vm will cause exception in vdsm logs
Summary: Adding new disk to active vm will cause exception in vdsm logs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: 3.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.5.1
Assignee: Adam Litke
QA Contact: Raz Tamir
URL:
Whiteboard: storage
: 1136766 (view as bug list)
Depends On:
Blocks: 1193195
TreeView+ depends on / blocked
 
Reported: 2014-06-25 08:52 UTC by Raz Tamir
Modified: 2016-02-10 19:43 UTC (History)
10 users (show)

Fixed In Version: v4.16.2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-22 20:31:11 UTC
oVirt Team: Storage
Embargoed:


Attachments (Terms of Use)
vdsm log (3.25 MB, text/plain)
2014-06-25 08:52 UTC, Raz Tamir
no flags Details
vdsm log (5.00 MB, text/plain)
2014-08-25 06:38 UTC, Raz Tamir
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 29677 0 master MERGED virt: Change log level for disk stats collection failure Never
oVirt gerrit 31536 0 ovirt-3.5 MERGED virt: Change log level for disk stats collection failure Never

Description Raz Tamir 2014-06-25 08:52:36 UTC
Created attachment 911980 [details]
vdsm log

Description of problem:
After each time I add disk to active vm, in vdsm log an exception is raised:


GuestMonitor-123::ERROR::2014-06-25 11:47:34,974::vm::376::vm.Vm::(_getDiskStats) vmId=`6c8ea9b4-645c-4653-b662-697c3d1f61ba`::Disk vdb stats not available
Traceback (most recent call last):
  File "/usr/share/vdsm/virt/vm.py", line 372, in _getDiskStats
    (eInfo[dName][1] - sInfo[dName][1]) / sampleInterval)
KeyError: u'vdb'
GuestMonitor-123::ERROR::2014-06-25 11:47:34,974::vm::418::vm.Vm::(_getDiskLatency) vmId=`6c8ea9b4-645c-4653-b662-697c3d1f61ba`::Disk vdb latency not available
Traceback (most recent call last):
  File "/usr/share/vdsm/virt/vm.py", line 416, in _getDiskLatency
    dLatency = _avgLatencyCalc(sInfo[dName], eInfo[dName])
KeyError: u'vdb'
GuestMonitor-123::ERROR::2014-06-25 11:47:34,975::vm::376::vm.Vm::(_getDiskStats) vmId=`6c8ea9b4-645c-4653-b662-697c3d1f61ba`::Disk vdb stats not available
Traceback (most recent call last):
  File "/usr/share/vdsm/virt/vm.py", line 372, in _getDiskStats
    (eInfo[dName][1] - sInfo[dName][1]) / sampleInterval)
KeyError: u'vdb'
GuestMonitor-123::ERROR::2014-06-25 11:47:34,975::vm::418::vm.Vm::(_getDiskLatency) vmId=`6c8ea9b4-645c-4653-b662-697c3d1f61ba`::Disk vdb latency not available
Traceback (most recent call last):
  File "/usr/share/vdsm/virt/vm.py", line 416, in _getDiskLatency
    dLatency = _avgLatencyCalc(sInfo[dName], eInfo[dName])
KeyError: u'vdb'


Version-Release number of selected component (if applicable):
vdsm-4.15.0-78.git349f848.el6.x86_64
libvirt-0.10.2-29.el6_5.7.x86_64


How reproducible:
100%

Steps to Reproduce:
1. run a vm
2. add new disk
3.

Actual results:
explained above

Expected results:
the disk should be added with no exceptions

Additional info:

Comment 1 Raz Tamir 2014-08-25 06:38:54 UTC
Created attachment 930341 [details]
vdsm log

Comment 2 Raz Tamir 2014-08-25 06:39:50 UTC
Still occurs - moving to assign

New vdsm logs attached

Comment 3 Allon Mureinik 2014-09-04 11:21:55 UTC
*** Bug 1136766 has been marked as a duplicate of this bug. ***

Comment 4 Adam Litke 2014-10-22 20:31:11 UTC
Fixed by ef6890a1 which appears in vdsm version 4.16.0.  oVirt-3.5 ships at least vdsm-4.16.7.


Note You need to log in before you can comment on or make changes to this bug.