RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1135341 - virt-who shows "TypeError" when it runs in VDSM and RHEVM mode
Summary: virt-who shows "TypeError" when it runs in VDSM and RHEVM mode
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-who
Version: 6.6
Hardware: x86_64
OS: All
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Radek Novacek
QA Contact: gaoshang
URL:
Whiteboard:
: 1135342 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-29 06:31 UTC by Liushihui
Modified: 2016-12-01 00:33 UTC (History)
5 users (show)

Fixed In Version: virt-who-0.10-7.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-14 07:13:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1513 0 normal SHIPPED_LIVE virt-who bug fix and enhancement update 2014-10-14 01:22:23 UTC

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


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