Bug 1246179 - EMS refresh against SCVMM provider returns bad fqdn for hypervisors
Summary: EMS refresh against SCVMM provider returns bad fqdn for hypervisors
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: 5.5.0
Assignee: Greg Blomquist
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-23 15:47 UTC by Thom Carlin
Modified: 2015-07-23 17:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-23 17:05:40 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:
tcarlin: automate_bug?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1236599 0 high CLOSED For SCVMM hypervisor, verifying host credentials throws EPIPE 2021-02-22 00:41:40 UTC

Internal Links: 1236599

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
Note You need to log in before you can comment on or make changes to this bug.