service try to contact zookeeper based on adress not ip

[Pierre Amadio]

i was trying to deploy juju charms on a private openstack cloud without success.

I was able to bootstrap, but when deploying a service such as mysql, it kept in pending state.

Logging on the service box, /var/log/juju/machine-agent.log show the following:

####################################
2012-07-24 07:54:31,545: twisted@ERROR: Unhandled error in Deferred:
2012-07-24 07:54:31,557: twisted@ERROR: Unhandled Error
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py",
line 1181, in unwindGenerator
    return _inlineCallbacks(None, gen, Deferred())
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py",
line 1039, in _inlineCallbacks
    result = g.send(result)
  File "/usr/lib/python2.7/dist-packages/juju/agents/base.py", line 238,
in startService
    yield self.connect()
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py",
line 1181, in unwindGenerator
    return _inlineCallbacks(None, gen, Deferred())
--- <exception caught here> ---
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py",
line 1039, in _inlineCallbacks
    result = g.send(result)
  File "/usr/lib/python2.7/dist-packages/juju/agents/base.py", line 208,
in connect
    self.config["zookeeper_servers"])
  File "/usr/lib/python2.7/dist-packages/txzookeeper/retry.py", line
302, in connect
    return self.client.connect(*args, **kw)
  File "/usr/lib/python2.7/dist-packages/txzookeeper/client.py", line
466, in connect
    self._servers, callback, self._session_timeout)
zookeeper.ZooKeeperException: Could not internally obtain zookeeper handle
####################################

tcpdump on the zookeeper node show there was no attempt to connect to it (connectoing manually with telnet worked).

Turns out the python process trying to connect to zookeper try to connect to the zookeeper machine is using its name (server-23 or whatever) but cannot resolved it.

Exceprt from a irc chat with hazmat:

<hazmat> melmoth, that might be the case for the zk address
<hazmat> the ip usage for openstack is primarily for unit level relations
<hazmat> the zk address is resolved using the provider given dns entry
<hazmat> we can should/switch that out to ip though
<hazmat> melmoth, would you mind filing a bug report for that
<melmoth> ok. on my TODO list :)

[Clint Byrum (clint-fewbar)]

The openstack native provider uses IP's only, so I don't think this bug is relevant anymore.