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):
Steps to Reproduce:
1. Register system to SAM server.
2. Configure virt-who run at hyperv mode
3. Restart virt-who service
4. Check the virt-who log at /var/log/rhsm/rhsm.log
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
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)
virt-who should send host/guest associate to SAM server, it also should display correct host/guest associate in the virt-who log.
It has the same problem when run virt-who at esx mode.
This issue has been fixed upstream:
Fixed in virt-who-0.10-4.el6.
Verified on virt-who-0.10-4.el6.noarch
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.