Bug 1082981

Created attachment 881250 [details]
The successful transaction on HyperV2008

Created attachment 881251 [details]
The error transaction on the HyperV2012

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Do the same test as bug description on RHEL5u11-Server-x64-20140603.0(kvm) + HyperV2012, The bug is still exist.

Test Env:
Hyper-V 2012 : 10.66.129.161
SAM server: 10.66.129.45 username/password:admin/admin

Version-Release number of selected component (if applicable):
subscription-manager-1.11.3-5.el5
python-rhsm-1.11.3-3.el5
virt-who-0.9-4.el5

Steps to Reproduce:
1. Install a Hyper-V 2012 on a physical machine which installed Windows Server 2012 R2 Datacenter.
2. Configure Hyper-V 2012 as README.hyperv file 
 https://git.fedorahosted.org/cgit/virt-who.git/tree/README.hyperv
3. Configure virt-who run at the hyperv mode. 
VIRTWHO_DEBUG=1
VIRTWHO_INTERVAL=5
VIRTWHO_HYPERV=1

VIRTWHO_HYPERV_OWNER=ACME_Corporation
VIRTWHO_HYPERV_ENV=Library
VIRTWHO_HYPERV_SERVER=10.66.129.161
VIRTWHO_HYPERV_USERNAME=administrator
VIRTWHO_HYPERV_PASSWORD=qwer1234P
4.Register system to SAM server and restart virt-who service
[root@hp-z220-03 ~]#subscription-manager register --username=admin --password=admin
[root@hp-z220-03 ~]# service virt-who restart
Stopping virt-who:                                         [FAILED]
Starting virt-who:                                         [  OK  ]
5.Check the virt-who log in the /var/log/rhsm/rhsm.log
#tail -f /var/log/rhsm/rhsm.log

2014-06-23 01:28:10,592 [WARNING]  @virt-who.py:547 - Listening for events is not available in VDSM, ESX, RHEV-M or Hyper-V mode
2014-06-23 01:28:10,750 [DEBUG]  @hyperv.py:172 - Hyper-V url: http://10.66.128.161:5985/wsman
2014-06-23 01:28:10,750 [DEBUG]  @virt-who.py:562 - Virt-who is running in hyperv mode
2014-06-23 01:28:10,751 [DEBUG]  @virt-who.py:569 - Starting infinite loop with 5 seconds interval and event handling
2014-06-23 01:28:10,755 [DEBUG]  @hyperv.py:222 - Using NTLM authentication
2014-06-23 01:28:10,867 [DEBUG]  @hyperv.py:249 - NTLM authentication successful
2014-06-23 01:28:10,931 [ERROR]  @virt-who.py:207 - Error in communication with virt backend, trying to recover:
Traceback (most recent call last):
  File "/usr/share/virt-who/virt-who.py", line 198, in _send
    virtualGuests = self.virt.getHostGuestMapping()
  File "/usr/share/virt-who/hyperv.py", line 277, in getHostGuestMapping
    uuid = hypervsoap.Enumerate("select BIOSGUID from Msvm_VirtualSystemSettingData where SettingType = 3")
  File "/usr/share/virt-who/hyperv.py", line 95, in Enumerate
    response = self.post(data)
  File "/usr/share/virt-who/hyperv.py", line 75, in post
    raise HyperVException("Communication with Hyper-V failed, HTTP error: %d" % response.status)
HyperVException: Communication with Hyper-V failed, HTTP error: 415

This bug should be fixed by rebase to virt-who-0.11-1.el7.

Verify it on virt-who-0.11-1.el7.noarch

Verified process:
Env:
Hyper-V 2012 : 10.66.128.26
SAM server: 10.66.129.124 username/password:admin/admin

Version-Release number of selected component (if applicable):
subscription-manager-1.13.3-1.el7.x86_64
python-rhsm-1.13.2.1-2.el7.x86_64
virt-who-0.11-1.el7.noarch

Steps to verify:
1. Install a Hyper-V 2012 on a physical machine which installed Windows Server 2012 R2 Datacenter.
2. Configure Hyper-V 2012 as README.hyperv file 
 https://git.fedorahosted.org/cgit/virt-who.git/tree/README.hyperv
3. Configure virt-who run at the hyperv mode. 
VIRTWHO_DEBUG=1
VIRTWHO_INTERVAL=5
VIRTWHO_HYPERV=1

VIRTWHO_HYPERV_OWNER=ACME_Corporation
VIRTWHO_HYPERV_ENV=Library
VIRTWHO_HYPERV_SERVER=10.66.128.26
VIRTWHO_HYPERV_USERNAME=administrator
VIRTWHO_HYPERV_PASSWORD=qwer1234P
4.Register system to SAM server and restart virt-who service
[root@dhcp-128-2 ~]# subscription-manager register --username=admin --password=admin
The system has been registered with ID: 240e7611-6fde-451c-8a24-282dde528024 
[root@dhcp-128-2 ~]# service virt-who restart
Redirecting to /bin/systemctl restart  virt-who.service

5.Check the virt-who log in the /var/log/rhsm/rhsm.log,it hasn't show any error log, Meanwhile, the hypervisor has been registered to SAM successfully.Therefore, Verify it.

#tail -f /var/log/rhsm/rhsm.log
2014-10-10 10:11:26,595 [INFO]  @virtwho.py:442 - Using virt-who configuration: virt-who
2014-10-10 10:11:26,596 [DEBUG]  @virtwho.py:170 - Starting infinite loop with 5 seconds interval
2014-10-10 10:11:26,724 [DEBUG]  @hyperv.py:208 - Hyper-V url: http://10.66.128.26:5985/wsman
2014-10-10 10:11:26,728 [DEBUG]  @hyperv.py:258 - Using NTLM authentication
2014-10-10 10:11:26,774 [DEBUG]  @hyperv.py:285 - NTLM authentication successful
2014-10-10 10:11:26,783 [DEBUG]  @hyperv.py:325 - Error when enumerating using root/virtualization namespace, trying root/virtualization/v2 namespace
2014-10-10 10:11:26,784 [DEBUG]  @hyperv.py:258 - Using NTLM authentication
2014-10-10 10:11:26,801 [DEBUG]  @hyperv.py:285 - NTLM authentication successful
2014-10-10 10:11:26,897 [INFO]  @subscriptionmanager.py:116 - Sending update in hosts-to-guests mapping: {'60527517-6284-7593-6AAB-75BF2A6375EF': []}
2014-10-10 10:11:28,013 [INFO]  @virtwho.py:164 - Created host: 48c16a13-d920-43a2-b72a-a812b9a899db with guests: []

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.

https://rhn.redhat.com/errata/RHSA-2015-0430.html