Bug 1432140

Summary: [RFE] virt-who should log when a duplicate hypervisor ID is discovered
Product: Red Hat Enterprise Linux 7 Reporter: Freddy Wissing <fwissing>
Component: virt-whoAssignee: William Poteat <wpoteat>
Status: CLOSED ERRATA QA Contact: Eko <hsun>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: bbuckingham, jhnidek, jsefler, khowell, rjerrido, tomckay, yuefliu
Target Milestone: pre-dev-freezeKeywords: FutureFeature, Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 10:47:13 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:

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