Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1389729 - virt-who incorrectly reports 'name' instead of 'hostname' for RHEV hosts
virt-who incorrectly reports 'name' instead of 'hostname' for RHEV hosts
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-who (Show other bugs)
Unspecified Unspecified
high Severity high
: rc
: ---
Assigned To: Chris Snyder
Jiri Herrmann
: Triaged
: 1412862 (view as bug list)
Depends On:
Blocks: 1473733
  Show dependency treegraph
Reported: 2016-10-28 06:44 EDT by Francisco Garcia
Modified: 2018-04-10 12:21 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Release Note
Doc Text:
*virt-who* now reads the 'address' field provided by RHEVM to discover and report the correct host name Previously, if the *virt-who* utility reported on a Red Hat Virtualization (RHV) host and the "hypervisor_id=hostname" option was used, *virt-who* displayed an incorrect host name value. This update ensures that *virt-who* reads the correct field value in the described circumstances and as a result, the proper host name is displayed.
Story Points: ---
Clone Of:
Last Closed: 2018-04-10 12:19:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
screenshot-Address (54.96 KB, image/png)
2018-01-03 00:47 EST, yuefliu
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
Github virt-who/virt-who/pull/73 None None None 2017-06-02 10:50 EDT
Red Hat Product Errata RHEA-2018:0895 None None None 2018-04-10 12:21 EDT

  None (edit)
Description Francisco Garcia 2016-10-28 06:44:32 EDT
Description of problem:

virt-who is using the 'name' field of the RHEV-produced xml inventory. Since that is a user-definable field, it causes issues when reporting back to Satellite 6.2 . Satellite 6.2 introduces strict hostname verification and then a FQDN should be provided by virt-who, as well as filter out underscore characters "_" . 

Version-Release number of selected component (if applicable):
virt-who  0.17-9.el7sat

How reproducible:
Always, as follows

Steps to Reproduce:
1. Add a RHEV hypervisor and set their name to  "my_host_name".
2. Verify that virt-who uses that field instead of "address" XML field
3. Verify that virt-who fails to report to Satellite 6.2 as "my_host_name" fails strict validation.

Actual results:

Expected results:
virt-who should report the 'address' field, which contains the DNS hostname of the hypervisor.

Additional info:

virt-who can be easily fixed by ammending the /usr/lib/python2.7/site-packages/virtwho/virt/rhevm/rhevm.py :

146             elif self.config.hypervisor_id == 'hostname':
147                 host_id = host.find('address').text
168             hosts[id] = virt.Hypervisor(hypervisorId=host_id, name=host.find('address').text, facts=facts)
Comment 2 Kevin Howell 2016-12-12 15:29:31 EST
We need to validate what versions of RHEV this is valid for.
Comment 3 Chris Snyder 2017-05-11 17:13:41 EDT
*** Bug 1412862 has been marked as a duplicate of this bug. ***
Comment 4 Francisco Garcia 2017-06-02 07:25:12 EDT
hi Kevin,

Just checked this is valid for 3.5 to 4.1. I'd say this is also valid in all RHEV 3.x series and given it'll EOL in September, we're won't be introducing any breaking change.

Is there anything else required to fix this?

Comment 6 yuefliu 2017-11-02 06:32:28 EDT
The bug still exists with virt-who-0.21.0-1.el7.noarch against RHEVM4.1
Comment 8 yuefliu 2018-01-03 00:47 EST
Created attachment 1376131 [details]
Comment 17 errata-xmlrpc 2018-04-10 12:19:53 EDT
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.


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