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.

Bug 1361434

Summary: [RHEL7] Virt-who should not add "." at the end of ESX hypervisor hostname if the domain name is not configured.
Product: Red Hat Enterprise Linux 7 Reporter: Ashish Humbe <ahumbe>
Component: virt-whoAssignee: Radek Novacek <rnovacek>
Status: CLOSED ERRATA QA Contact: Eko <hsun>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2CC: hartsjc, ktordeur, mjahangi, ovasik, shihliu, vanhoof, vmeghana, xdmoon
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: virt-who-0.17-7.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 05:10:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1203710, 1385841    

Comment 2 Radek Novacek 2016-08-09 08:03:03 UTC 
This is fixed in virt-who-0.17-7.el7.
Comment 4 Eko 2016-09-22 03:01:54 UTC 
verified in virt-who-0.17-10.el7

===== if with ESX Domain Name =========
2016-09-21 23:01:05,443 [virtwho.main DEBUG] MainProcess(32284):MainThread @subscriptionmanager.py:hypervisorCheckIn:196 - Host-to-guest mapping: {
    "bootp-73-5-222.rhts.eng.pek2.redhat.com": [], 
    "bootp-73-5-233.rhts.eng.pek2.redhat.com": [
        {
            "guestId": "421a578c-1d65-3813-86da-50810d8c83ef", 
            "state": 1, 
            "attributes": {
                "active": 1, 
                "virtWhoType": "esx"
            }
        }
    ]
}
2016-09-21 23:01:06,564 [virtwho.main DEBUG] MainProcess(32284):MainThread @executor.py:send_report:101 - Report for config "test-esx" sent


===== if without ESX Domain Name ========
2016-09-21 22:59:09,736 [virtwho.main DEBUG] MainProcess(32256):MainThread @subscriptionmanager.py:hypervisorCheckIn:196 - Host-to-guest mapping: {
    "bootp-73-5-222": [], 
    "bootp-73-5-233": [
        {
            "guestId": "421a578c-1d65-3813-86da-50810d8c83ef", 
            "state": 1, 
            "attributes": {
                "active": 1, 
                "virtWhoType": "esx"
            }
        }
    ]
}
2016-09-21 22:59:13,319 [virtwho.main DEBUG] MainProcess(32256):MainThread @executor.py:send_report:101 - Report for config "test-esx" sent
Comment 7 errata-xmlrpc 2016-11-04 05:10:14 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.

https://rhn.redhat.com/errata/RHBA-2016-2387.html