Bug 1135341

Summary: virt-who shows "TypeError" when it runs in VDSM and RHEVM mode
Product: Red Hat Enterprise Linux 6 Reporter: Liushihui <shihliu>
Component: virt-whoAssignee: Radek Novacek <rnovacek>
Status: CLOSED ERRATA QA Contact: gaoshang <sgao>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.6CC: liliu, lmiksik, ovasik, rbalakri, sgao
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: virt-who-0.10-7.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-14 07:13:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Liushihui 2014-08-29 06:31:06 UTC
Description of problem:
Configure virt-who run at VDSM mode, then run virt-who, it will show "TypeError: __init__() takes exactly 2 arguments (3 given)" when it communication with virtualization backend

Version-Release number of selected component (if applicable):
subscription-manager-1.12.12-1.el6.x86_64
python-rhsm-1.12.5-1.el6.x86_64
virt-who-0.10-6.el6.noarch
katello-headpin-1.4.3.26-1.el6sam_splice.noarch
candlepin-0.9.6.5-1.el6sam.noarch

How reproducible:
Always

Steps to Reproduce:
1. Register system to SAM server.
2. Configure virt-who run at VDSM mode 
VIRTWHO_DEBUG=1
VIRTWHO_BACKGROUND=1
VIRTWHO_INTERVAL=10
VIRTWHO_VDSM=1
3. Restart vdsmd service, then check the vdsmd service run normally.
[root@hp-z220-08 ~]# service vdsmd restart
[root@hp-z220-08 ~]# service vdsmd status
VDS daemon server is running
4. Restart virt-who service
5. Check the virt-who log at /var/log/rhsm/rhsm.log

Actual results:
2014-08-29 14:28:05,618 [INFO]  @virtwho.py:442 - Using virt-who configuration: virt-who
2014-08-29 14:28:05,618 [DEBUG]  @virtwho.py:170 - Starting infinite loop with 10 seconds interval
2014-08-29 14:28:05,710 [ERROR]  @virtwho.py:118 - Error in communication with virtualization backend, trying to recover:
Traceback (most recent call last):
  File "/usr/share/virt-who/virtwho.py", line 111, in _send
    virtualGuests = self._readGuests(config)
  File "/usr/share/virt-who/virtwho.py", line 141, in _readGuests
    virt = Virt.fromConfig(self.logger, config)
  File "/usr/share/virt-who/virt/virt.py", line 63, in fromConfig
    return subsubcls(logger, config)
TypeError: __init__() takes exactly 2 arguments (3 given)
2014-08-29 14:28:05,711 [ERROR]  @virtwho.py:121 - Unable to recover, retry in 10 seconds.

Expected results:
It shouldn't show up any error messages.Virt-who should run normally under the VDSM mode.

Additional info:

Comment 2 Radek Novacek 2014-08-29 06:53:05 UTC
*** Bug 1135342 has been marked as a duplicate of this bug. ***

Comment 3 Radek Novacek 2014-08-29 07:02:46 UTC
Same issue happens in the RHEVM mode:
2014-08-29 14:36:37,340 [ERROR]  @virtwho.py:118 - Error in communication with virtualization backend, trying to recover:
Traceback (most recent call last):
  File "/usr/share/virt-who/virtwho.py", line 111, in _send
    virtualGuests = self._readGuests(config)
  File "/usr/share/virt-who/virtwho.py", line 141, in _readGuests
    virt = Virt.fromConfig(self.logger, config)
  File "/usr/share/virt-who/virt/virt.py", line 63, in fromConfig
    return subsubcls(logger, config)
TypeError: __init__() takes exactly 5 arguments (3 given)

Comment 4 Radek Novacek 2014-08-29 07:45:44 UTC
Fix for this issue has been submitted to the upstream repo:

https://git.fedorahosted.org/cgit/virt-who.git/commit/?id=69dcffe281aa1333cf6d319b7067b7476428d308

Comment 6 Radek Novacek 2014-09-01 12:36:15 UTC
Fixed in virt-who-0.10-7.el6.

Comment 8 Liushihui 2014-09-05 06:52:04 UTC
Verified on virt-who-0.10-7.el6.noarch

Comment 9 errata-xmlrpc 2014-10-14 07:13:29 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/RHBA-2014-1513.html