UAA returns error: getaddrinfo: Name or service not known

[skuppa]

With latest code, I was able to deploy bosh-lite successfully but I am trying to login using cf but it fails with error that Name or service not known. Any suggestion?

devops@malligai2:~/git/cf/cf-samples/hello$ 
devops@malligai2:~/git/cf/cf-samples/hello$ cf target
Target Information (where will apps be pushed):
  CF instance: http://api.10.244.0.34.xip.io (API version: 2)
  user: N/A
  target app space: N/A (org: N/A)
devops@malligai2:~/git/cf/cf-samples/hello$ cf login
target: http://api.10.244.0.34.xip.io

Time of crash:
  2013-11-05 23:54:30 -0800

CF::UAA::BadTarget: error: getaddrinfo: Name or service not known

cf-uaa-lib-2.0.0/lib/uaa/http.rb:161:in `rescue in net_http_request'
cf-uaa-lib-2.0.0/lib/uaa/http.rb:149:in `net_http_request'
cf-uaa-lib-2.0.0/lib/uaa/http.rb:137:in `request'
cf-uaa-lib-2.0.0/lib/uaa/http.rb:119:in `http_get'
cf-uaa-lib-2.0.0/lib/uaa/http.rb:89:in `json_get'
cf-uaa-lib-2.0.0/lib/uaa/info.rb:70:in `server'

[syslxg]

if the problem is still there, please try

cf target http://api.10.244.0.34.xip.io  --trace 
cf login --trace

and post the outputs

[mkocher]

Dup of #34

We're pretty sure this is caused by a state the VM can get into where it has no external internet access, or extremely slow external internet access. Halting the vm and bringing it back up again may make the problem go away.

We'd need steps to reproduce the problem, or an explanation of why we're seeing the network not working on the vagrant vm in order to fix this.

[skuppa]

Thanks Gary and mkocher.

The xip.io does not resolve to ip address due to resolv.conf points to 127.0.01 and it looks like a bug in ubuntu 12.04, https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/933723. I removed nameserver 127.0.0.1 from resolv.conf and added nameserver 8.8.8.8 then problem resolved.