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 1432140 - [RFE] virt-who should log when a duplicate hypervisor ID is discovered
Summary: [RFE] virt-who should log when a duplicate hypervisor ID is discovered
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-who
Version: 7.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: pre-dev-freeze
: ---
Assignee: William Poteat
QA Contact: Eko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-14 15:45 UTC by Freddy Wissing
Modified: 2022-03-13 14:13 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 10:47:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github candlepin virt-who pull 152 0 None None None 2020-07-13 03:43:34 UTC
Red Hat Product Errata RHBA-2018:3169 0 None None None 2018-10-30 10:48:02 UTC

Description Freddy Wissing 2017-03-14 15:45:27 UTC
Description of problem:

When virt-who discovers a duplicate hostname (such as a host incorrectly identifying itself as "localhost" it does not log any errors and appears to just overwrite the previous host with that name.   

Version-Release number of selected component (if applicable):


How reproducible:

Requires an incorrectly configured vmware environment.

Steps to Reproduce:
1. Set vmware hypervisors to identify themselves as 'localhost' when queried by virt-who.

2. virt-who will run, and return with name 'localhost.'

3. observe that no error is thrown, nor a log statement written.  The data of that host is either discarded or the prior host reported with that name is overwritten.

Expected results:

virt-who should log on a duplicate hostname, and should throw a warning when 'localhost' specifically is detected as a host id/hostname.


Additional info:

Comment 2 Kevin Howell 2017-06-26 15:13:30 UTC
The problem is that we are not warning when this occurs.

Comment 10 errata-xmlrpc 2018-10-30 10:47:13 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://access.redhat.com/errata/RHBA-2018:3169


Note You need to log in before you can comment on or make changes to this bug.