Created attachment 1189376 [details]
customer tested patch

Had customer apply attached patch and reported things working for them now.

# rpm -q virt-who
virt-who-0.16-8.el6.noarch
# service virt-who stop
# cd /
# cat /root/bz1361445.patch | patch -p1 -b -z .bz1361445
patching file usr/share/virt-who/virt/esx/esx.py
# service virt-who start


Not sure related or not yet, but seems virt entitlements are not correct yet.  So may need additional steps after fix if is related

Fixed in virt-who-0.18-1.el6.

The bug doesn't reproduce on RHEL-6.9-20170202.0 (virt-who-0.18-3.el6.noarch) with satellite6.2.6, virt-who can correctelly report hypervisor hostname without "." to the sat server when the hostname is configured without domain name, just "server". So verified it.


*******/rhsm.log*******
2017-02-08 04:03:32,824 [virtwho.main DEBUG] MainProcess(10488):MainThread @subscriptionmanager.py:hypervisorCheckIn:196 - Host-to-guest mapping: {
    "host1.rhts.eng.pek2.redhat.com": [
        {
            "guestId": "421d1083-25f6-f8d0-b31a-f98ec7e4a87c", 
            "state": 5, 
            "attributes": {
                "active": 0, 
                "virtWhoType": "esx"
            }
        }
    ], 
    "server": [
        {
            "guestId": "421de5a3-a462-2fae-656b-094173934a0d", 
            "state": 1, 
            "attributes": {
                "active": 1, 
                "virtWhoType": "esx"
            }
        }, 
        {
            "guestId": "421ce0fc-af56-2476-0edc-20deed295e37", 
            "state": 5, 
            "attributes": {
                "active": 0, 
                "virtWhoType": "esx"
            }
        }
    ]
}
2017-02-08 04:03:35,158 [virtwho.main DEBUG] MainProcess(10488):MainThread @executor.py:send_report:102 - Report for config "sate-esx" sent

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/RHBA-2017-0675.html