Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1361431 - Virt-who should not add
Summary: Virt-who should not add
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-who
Version: 7.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Radek Novacek
QA Contact: Eko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-29 05:36 UTC by Ashish Humbe
Modified: 2016-12-01 00:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-29 06:19:27 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Ashish Humbe 2016-07-29 05:36:34 UTC
Description of problem:

If the domain name is not configured correctly on the ESX hypervisor then virt-who report hypervisor hostname as "server1." instead of "server1". In satellite v 6.2 the hostname validation if implemented so it does not allow to save the hypervisor entry with "." at the end. 

As per discussion with Radek, this issue is because of the below code.

elif self.config.hypervisor_id == 'hostname':
uuid ="%(config.network.dnsConfig.hostName)s.%(config.network.dnsConfig.domainName
)s" % host


After discussion the change is made in the upstream virt-who code, so the extra "." will not be added in the hostname if domain name is not set. 

https://github.com/virt-who/virt-who/commit/418474a4231c9dba1bb60b0168c28be283acc1a7


How reproducible:
Always if the domain name is not configured on the ESX hypervisor



Creating this bugzilla to merge this change in latest version of virt-who package in RHEL 7.


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