Scott Moser 31d56c51a4 fix / workaround potential for socket.getaddrinfo to raise socket.error
As reported in bug 1154599, I'm seeing this on my desktop system:
$ python -c \
  'from cloudinit import util; print util.is_resolvable("brickies.neiit")'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "cloudinit/util.py", line 865, in is_resolvable
    socket.SOCK_STREAM, socket.AI_CANONNAME)
2013-03-13 10:43:40 -04:00
..
2013-03-07 16:47:54 -05:00
2013-03-07 16:47:54 -05:00
2013-03-07 17:13:05 -05:00
2013-03-07 17:13:05 -05:00
2013-03-07 16:47:54 -05:00
2013-03-06 19:24:05 -08:00
2012-09-24 16:59:23 -04:00
2012-09-28 16:35:53 -04:00
2013-03-07 14:54:25 -05:00
2013-03-07 16:27:47 -05:00
2012-11-14 13:32:14 -08:00