[----] E, [2017-03-25T06:38:18.640082 #3557:7bd130] ERROR -- : excon.error #<Excon::Error::Socket: getaddrinfo: Name or service not known (SocketError)>This also shows up in the OpenStack Provider in the WebUI of the ManageIQ as Socket: getaddrinfo: Name or service not known (SocketError)>
I was using the Newton Installation on the OpenStack and had to use the IP addresses of the controller and the compute nodes for openstack.
Deployment of OpenStack Newton was using the packstack and had to use IP addresses for the controller nodes and the compute nodes owing to a bug in PackStack for Newton.
The below link can be informative for the packstack issue in Newton OpenStack
But with that as I had the ManageIQ appliance of VMware and had set it to an IP address in the same subnet as the OpenStack controller, I was successfully able to add the OpenStack provider under cloud providers in the ManageIQ.
But post that each attempt of having the synchronizing the current status of the provider threw me the error "getaddrinfo: Name or service not known (SocketError)" in the ManageIQ UI as well as in the appliance's /var/log/manageiq/fog.log
The WorkAround:
The workaround was to have an entry for the OpenStack controller IP address and FQDN entry in the /etc/hosts file of the ManageIQ appliance.
Please note: I was not using any DNS service at the time, and for host name resolution by the ManageIQ appliance I had to rely on /etc/hosts on the ManageIQ server. Not sure if there had been a DNS server to resolve the IP address of the controller to the ManageIQ host this problem would have arose or not.