Bug 1229426 - Host provisioning fails - [SocketError]: getaddrinfo: Name or service not known
Summary: Host provisioning fails - [SocketError]: getaddrinfo: Name or service not known
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: Brandon Dunne
QA Contact: Nandini Chandra
URL:
Whiteboard: host:provision
Depends On:
Blocks: 1291876
TreeView+ depends on / blocked
 
Reported: 2015-06-08 17:23 UTC by Nandini Chandra
Modified: 2017-06-07 18:46 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1291876 (view as bug list)
Environment:
Last Closed: 2017-06-07 18:46:05 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Nandini Chandra 2015-06-08 17:23:54 UTC
Description of problem:
-----------------------
Provisioning of VMware hosts fails with this error message:

[[SocketError]: getaddrinfo: Name or service not known 
(https://<name>:443)] encountered during phase [configure_destination]

Snippet from automate.log:

[----] I, [2015-06-08T05:14:11.700751 #5985:6a5ea0]  INFO -- : MIQ(BottleneckEvent-generate_future_events) Generating future bottleneck events for: [HostVmwareEsx - cfme-esx-55-04.cfme.lab.eng.rdu2.redhat.com]...
[----] E, [2015-06-08T05:14:11.778658 #2681:7dfe9c] ERROR -- : Q-task_id([miq_host_provision_1]) MIQ(MiqHostProvision#provision_error) [[SocketError]: getaddrinfo: Name or service not known (https://do-not-use-vmware:443)] encountered during phase [configure_destination]
[----] E, [2015-06-08T05:14:11.778827 #2681:7dfe9c] ERROR -- : Q-task_id([miq_host_provision_1]) /opt/rh/cfme-gemset/gems/httpclient-2.5.3.3/lib/httpclient/session.rb:815:in `initialize'
/opt/rh/cfme-gemset/gems/httpclient-2.5.3.3/lib/httpclient/session.rb:815:in `new'
/opt/rh/cfme-gemset/gems/httpclient-2.5.3.3/lib/httpclient/session.rb:815:in `create_socket'
/opt/rh/cfme-gemset/gems/httpclient-2.5.3.3/lib/httpclient/session.rb:763:in `block in connect'
/opt/rh/ruby200/root/usr/share/ruby/timeout.rb:66:in `timeout'
/opt/rh/ruby200/root/usr/share/ruby/timeout.rb:97:in `timeout'
/opt/rh/cfme-gemset/gems/httpclient-2.5.3.3/lib/httpclient/session.rb:762:in `connect'
/opt/rh/cfme-gemset/gems/httpclient-2.5.3.3/lib/httpclient/session.rb:620:in `query'
/opt/rh/cfme-gemset/gems/httpclient-2.5.3.3/lib/httpclient/session.rb:164:in `query'
/opt/rh/cfme-gemset/gems/httpclient-2.5.3.3/lib/httpclient.rb:1161:in `do_get_block'
/opt/rh/cfme-gemset/gems/httpclient-2.5.3.3/lib/httpclient.rb:962:in `block in do_request'
/opt/rh/cfme-gemset/gems/httpclient-2.5.3.3/lib/httpclient.rb:1059:in `protect_keep_alive_disconnected'
/opt/rh/cfme-gemset/gems/httpclient-2.5.3.3/lib/httpclient.rb:961:in `do_request'
/opt/rh/cfme-gemset/gems/httpclient-2.5.3.3/lib/httpclient.rb:823:in `request'
/opt/rh/cfme-gemset/gems/httpclient-2.5.3.3/lib/httpclient.rb:726:in `post'
/opt/rh/cfme-gemset/bundler/gems/handsoap-daec1277652f/lib/handsoap/service.rb:280:in `dispatch'
/opt/rh/cfme-gemset/bundler/gems/handsoap-daec1277652f/lib/handsoap/service.rb:192:in `invoke'
/var/www/miq/lib/VMwareWebService/VimService.rb:878:in `retrieveServiceContent'
/var/www/miq/lib/VMwareWebService/VimService.rb:21:in `initialize'
/var/www/miq/lib/VMwareWebService/MiqVimClientBase.rb:33:in `initialize'
/var/www/miq/lib/VMwareWebService/MiqVimInventory.rb:23:in `initialize'
/var/www/miq/lib/VMwareWebService/MiqVim.rb:24:in `initialize'
/var/www/miq/lib/util/miq_fault_tolerant_vim.rb:181:in `new'
/var/www/miq/lib/util/miq_fault_tolerant_vim.rb:181:in `_connect_without_broker'
/var/www/miq/lib/util/miq_fault_tolerant_vim.rb:174:in `block in _connect'
/var/www/miq/lib/util/miq_fault_tolerant_vim.rb:79:in `_execute_without_broker'


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


How reproducible:
-----------------
Always


Steps to Reproduce:
------------------
1.Attempt to provision a VMware host.


Actual results:
--------------
Host provisioning fails


Expected results:
----------------
Host provisioning should succeed.


Additional info:
----------------
This issue doesn't occur in CFME 5.3.

Comment 2 Brandon Dunne 2015-06-17 13:52:08 UTC
It looks like the hostname "do-not-use-vmware" can not be resolved, do you have a hosts entry for this?

Comment 3 Nandini Chandra 2015-08-17 11:25:12 UTC
1)I placed an entry for "do-not-use-vmware" in /etc/hosts on my CFME appliance and it then failed with this error message:

evm.log:[----] E, [2015-08-17T05:46:55.438506 #12359:9b1ea0] ERROR -- : Q-task_id([miq_host_provision_5]) MIQ(MiqHostProvision#provision_error) [[VimFault]: Cannot contact the specified host (do-not-use-vmware). The host may not be available on the network, a network configuration problem may exist, or the management services on this host may not be responding.] encountered during phase [configure_destination]

evm.log:[----] E, [2015-08-17T05:46:55.438721 #12359:9b1ea0] ERROR -- : Q-task_id([miq_host_provision_5]) (druby://127.0.0.1:48182) /var/www/miq/lib/VMwareWebService/MiqVimInventory.rb:1870:in `waitForTask'

2)Snippet from vpxa.log from the VMware host:
2015-08-17T09:40:31.592Z [FFF40B70 warning 'Default'] Failed to connect socket; <io_obj p:0x1f3b1ce8, h:17, <TCP '0.0.0.0:0'>, <TCP '127.0.0.1:4
2015-08-17T09:40:31.592Z [FFF40B70 error 'HttpConnectionPool-000000'] [ConnectComplete] Connect failed to <cs p:1f3ae710, TCP:localhost:443>; cn
2015-08-17T09:40:31.593Z [FFEFD1A0 error 'httphttpUtil'] [HttpUtil::ExecuteRequest] Error in sending request - Connection refused
2015-08-17T09:40:31.593Z [FFEFD1A0 error 'hostdcnx'] [VpxaHalCnxHostagent] Failed to discover version: vim.fault.HttpFault
2015-08-17T09:40:31.593Z [FFEFD1A0 warning 'hostdcnx'] [VpxaHalCnxHostagent] Could not resolve version for authenticating to host agent

3)This is being tested on ESX 5.5(through both CFME 5.3 and CFME 5.4)

4)The kickstart file used for host provisioning on CFME 5.4 and CFME 5.3 is the same.

5)I also did a stateless host provision so that the PXE files could be retained.I found that the kickstart file has a Post install callback URL.So,going by this,the host installation does complete.I can also access the web service on the newly provisioned ESX host.

Comment 4 Nandini Chandra 2015-08-17 11:31:28 UTC
Since this issue doesn't occur in 5.3,is it be possible that the merging of Host Name and IP address fields in the 'Add new host' form in 5.4 could be somehow messing this up?The two fields have been replaced by this single field:
Host Name (or IPv4 or IPv6 address)

Additionally,QE uses the same kickstart script for host provisioning in 5.3 and 5.4.The host provisioning has been tested on ESX 5.5 through 5.3 and 5.4.

Comment 7 Brandon Dunne 2016-03-22 14:05:15 UTC
I don't think this is caused by the merging of Hostname and IP address.  I have not yet reproduced this issue, so I don't know the cause.

Comment 8 Chris Pelland 2017-06-07 18:46:05 UTC
This BZ has been closed since it was opened on a version of CloudForms that has reached the end of its lifecycle.  If you find that this bug is still relevant, please open a new BZ against the relevant supported version of CloudForms.


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