Bug 893356

Summary: Exception while starting vdsmd service for the first time. Although vdsmd has been started successfully.
Product: Red Hat Enterprise Virtualization Manager Reporter: Leonid Natapov <lnatapov>
Component: vdsmAssignee: Yaniv Bronhaim <ybronhei>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.2.0CC: abaron, bazulay, dyasny, hateya, iheim, lpeer, pstehlik, sgrinber, ykaul
Target Milestone: ---Keywords: Regression
Target Release: 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-07 12:55:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Leonid Natapov 2013-01-09 08:08:33 UTC 
After manually installing vdsm package got the following exception while first start of a new vdsmd.

Founf while testing preint ticket https://engineering.redhat.com/trac/preint/ticket/847

[root@purple-vds3 ~]# service vdsmd start
 Stopping libvirtd daemon:                                  [  OK  ]
 Configuring libvirt for vdsm...
 Starting iscsid: 
 diff: /etc/init/libvirtd.conf: No such file or directory
 Exception in thread libvirtEventLoop (most likely raised during interpreter shutdown):
 Traceback (most recent call last):
     File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner
     File "/usr/lib64/python2.6/threading.py", line 484, in run
     File "/usr/lib64/python2.6/site-packages/vdsm/libvirtev.py", line 419, in virEventLoopPureRun
     File "/usr/lib64/python2.6/site-packages/vdsm/libvirtev.py", line 239, in run_loop
     File "/usr/lib64/python2.6/site-packages/vdsm/libvirtev.py", line 229, in run_once
  <type 'exceptions.AttributeError'>: 'NoneType' object has no attribute 'error'
  Starting up vdsm daemon: 
  vdsm start                                                 [  OK  ]
Comment 6 Leonid Natapov 2013-01-10 09:01:48 UTC 
yes,it's a regression.
Comment 10 Leonid Natapov 2013-02-14 13:14:32 UTC 
vdsm up after the exception.
Comment 12 Yaniv Bronhaim 2013-02-21 10:33:23 UTC 
I added a patch that removes the unnassacery warning:
 diff: /etc/init/libvirtd.conf: No such file or directory
please notify me if the exception is still raised and in what versions.
Comment 13 Barak 2013-03-07 12:55:29 UTC 
We can't reproduce it, and still waiting on the NEEDINFO