Bug 1246179

Summary:	EMS refresh against SCVMM provider returns bad fqdn for hypervisors
Product:	Red Hat CloudForms Management Engine	Reporter:	Thom Carlin <tcarlin>
Component:	Providers	Assignee:	Greg Blomquist <gblomqui>
Status:	CLOSED NOTABUG	QA Contact:	Dave Johnson <dajohnso>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.4.0	CC:	jfrey, jhardy, obarenbo
Target Milestone:	GA	Flags:	tcarlin: automate_bug?
Target Release:	5.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-23 17:05:40 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 Thom Carlin 2015-07-23 15:47:29 UTC

Description of problem:

EMS refresh returns the incorrect fqdn.

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

5.4.1.0.20150717083323_6ed7e1c

How reproducible:

100% for this environment

Steps to Reproduce:
1. Discover SCVMM provider
2. Supply credentials
3. Refresh Relationships and Power States
4. For each host, check fqdn

Actual results:

Incorrect fqdn (with domain added)

Expected results:

Correct fqdn

Additional info:

During validation of 1236599, we discovered the actual issue was in EMS refresh.

Comment 3 Thom Carlin 2015-07-23 17:05:40 UTC

It turns out in our case, the actual *actual* issue was environmental :-)

SCVMM returns the hypervisors with the AD domain prefixed.  So if hypervisor "foo" is in domain "bar" which is in "example.com", the returned host fqdn is foo.bar.example.com.

foo.bar.example.com needs to be resolvable by DNS.  In our case, we had an additional problem: it was not.

Workaround: Edit /etc/resolv.conf on the CFME appliance(s) to include AD DNS as first entry.

Verify: nslookup host_fqdn