Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1112998

Summary: Adding new disk to active vm will cause exception in vdsm logs
Product: [Retired] oVirt Reporter: Raz Tamir <ratamir>
Component: vdsmAssignee: Adam Litke <alitke>
Status: CLOSED CURRENTRELEASE QA Contact: Raz Tamir <ratamir>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.5CC: acanan, amureini, bazulay, bugs, gklein, iheim, mgoldboi, ogofen, rbalakri, yeylon
Target Milestone: ---   
Target Release: 3.5.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: v4.16.2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-22 20:31:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1193195    
Attachments:
Description Flags
vdsm log
none
vdsm log none

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.