Bug 695244

Summary: [vdsm] TypeError: 'NoneType' object is unsubscriptable as block Stats returns null
Product: Red Hat Enterprise Linux 6 Reporter: Haim <hateya>
Component: vdsmAssignee: Eduardo Warszawski <ewarszaw>
Status: CLOSED ERRATA QA Contact: Haim <hateya>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2CC: abaron, bazulay, danken, dnaori, ewarszaw, iheim, mgoldboi, sgrinber, yeylon, ykaul
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: vdsm-4.9-65 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 07:14:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Haim 2011-04-11 07:23:56 UTC
Description of problem:

error: 

Thread-36::ERROR::2011-04-11 09:08:44,678::utils::431::vm.Vm::(run) vmId=`c3542f6d-282d-4928-9923-541ff9a96484`::Traceback (most recent call last):
  File "/usr/share/vdsm/utils.py", line 421, in run
    sample = self.sample()
  File "/usr/share/vdsm/vm.py", line 137, in sample
    s = self.VmSampleClass(self._pid, self._ifids, self._vm)
  File "/usr/share/vdsm/libvirtvm.py", line 70, in __init__
    self.hdssample = vm.HdsSampleClass(vm)
  File "/usr/share/vdsm/libvirtvm.py", line 42, in __init__
    self.hds[d.name] = HdSample(vm, d.name)
  File "/usr/share/vdsm/libvirtvm.py", line 33, in __init__
    self.rdb = bs[1]
TypeError: 'NoneType' object is unsubscriptable

scenario: 

vdsm losses connection to libvirt, fails to take itself down, but continue to send block-stats over running VMs to libvirt, which doesn't answer, which results this error. 

please catch and handle this exception.

Comment 4 Haim 2011-05-17 10:59:43 UTC
verified, tested libvirt restart, stop, kill -STOP, vdsmd restart, no error. 

vdsm-4.9-66.el6.x86_64

Comment 5 errata-xmlrpc 2011-12-06 07:14:12 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2011-1782.html