I ran into this one last week. I was trying to tie my vCop’s instance into vCloud director with the vCloud adapter. I tried using the hostname / ip without any success. Some review of the logs for the adapter showed:
2013-08-08 14:57:50,272 ERROR [Collector worker thread 21] (171) com.integrien.adapter3.vcloud.VCloudAdapter.login - Exception occurred in login: com.vmware.vcloud.sdk.VCloudRuntimeException: org.apache.http.NoHttpResponseException: The target server failed to respond
I just love java errors… I will spare you all the crap that came after. The problem was simple but I had not expected it… DNS resolution was not working. I did not believe it… why would I need DNS when I was using the ip address of my systems. Well it’s a little complex by vcloud is three cells frontended by a F5 load balancer. I was using the ip address of the load balancer but the public URL in VCD was set to a DNS name. When you visit the ip address it redirects you and vcop’s to https://fqdn/vcloud this redirection using DNS was causing the failure. So we just have to get the linux appliances to see DNS.
- Login as root on both the UI and analytics machine
- Change the file /etc/sys/esxiconfig/network/configs
- Add the following line
- Run the following command to sync to /etc/resolv.conf
- netconfig update -f
Then it should work. Enjoy.