Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Configure virt-who run at hyperv mode or esx mode, then run virt-who, it will failed to connect with subscription-manager
Version-Release number of selected component (if applicable):
subscription-manager-1.12.4-1.el6.x86_64
python-rhsm-1.12.4-1.el6.x86_64
virt-who-0.10-3.el6.noarch
katello-headpin-1.4.3.26-1.el6sam_splice.noarch
candlepin-0.9.6.4-1.el6sam.noarch
How reproducible:
Always
Steps to Reproduce:
1. Register system to SAM server.
2. Configure virt-who run at hyperv mode
VIRTWHO_DEBUG=1
VIRTWHO_BACKGROUND=1
VIRTWHO_INTERVAL=5
VIRTWHO_HYPERV=1
VIRTWHO_HYPERV_OWNER=ACME_Corporation
VIRTWHO_HYPERV_ENV=Library
VIRTWHO_HYPERV_SERVER=10.66.128.173
VIRTWHO_HYPERV_USERNAME=administrator
VIRTWHO_HYPERV_PASSWORD=qwer1234P
3. Restart virt-who service
4. Check the virt-who log at /var/log/rhsm/rhsm.log
Actual results:
virt-who failed to send host/guest associate to SAM Server.
In the virt-who log ,it will pop up error message as the following:
2014-07-28 14:16:00,088 [INFO] @virtwho.py:442 - Using virt-who configuration: virt-who
2014-07-28 14:16:00,088 [DEBUG] @virtwho.py:170 - Starting infinite loop with 5 seconds interval
2014-07-28 14:16:00,219 [DEBUG] @hyperv.py:208 - Hyper-V url: http://10.66.128.173:5985/wsman
2014-07-28 14:16:00,221 [DEBUG] @hyperv.py:258 - Using NTLM authentication
2014-07-28 14:16:00,237 [DEBUG] @hyperv.py:285 - NTLM authentication successful
2014-07-28 14:16:01,345 [ERROR] @virtwho.py:133 - Error in communication with subscription manager, trying to recover:
Traceback (most recent call last):
File "/usr/share/virt-who/virtwho.py", line 125, in _send
self._sendGuests(config, virtualGuests)
File "/usr/share/virt-who/virtwho.py", line 154, in _sendGuests
result = manager.hypervisorCheckIn(config, virtualGuests)
TypeError: hypervisorCheckIn() takes at least 4 arguments (3 given)
Expected results:
virt-who should send host/guest associate to SAM server, it also should display correct host/guest associate in the virt-who log.
Additional info:
It has the same problem when run virt-who at esx mode.
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