client hangs on write about python-etcd HOT 5 CLOSED

Another info, after timeout traceback was:

Traceback (most recent call last):
  File "scripts/etcd_test.py", line 9, in <module>
    print client.write('/writetest', 'TESTSTRING')
  File "/usr/lib/python2.7/site-packages/python_etcd-0.3.2-py2.7.egg/etcd/client.py", line 272, in write
    response = self.api_execute(path, method, params=params)
  File "/usr/lib/python2.7/site-packages/python_etcd-0.3.2-py2.7.egg/etcd/client.py", line 581, in api_execute
    self._base_uri = self._next_server()
  File "/usr/lib/python2.7/site-packages/python_etcd-0.3.2-py2.7.egg/etcd/client.py", line 539, in _next_server
    raise etcd.EtcdException('No more machines in the cluster')
etcd.EtcdException: No more machines in the cluster

so it has troubles in writing to etcd db for some reason. Is this library tested with etcd 0.4.6?

from python-etcd.

Per the readme it looks like the client is only supporting the 2.0 release candidate versions and up now: "Install etcd (0.2.rc1 or later). This version of python-etcd will only work correctly with the etcd API version 2".

I wonder with you using 0.4.6 if that is the issue? I tested with the latest python-etcd source code, etcd 2.0.0 RC1 and Python 3.4.2 and didn't have any issues.

from python-etcd.

I'm encountering a similar problem.
I think it has something to do with etcd 0.4.6 returning a 307 (HTTP/1.1 307 Temporary Redirect) and urllib3 not following that on a PUT request.

@veverjak Were you running python-etcd through an SSH tunnel?

from python-etcd.

Nope, it was called from docker container running on CoreOS host.
I was connecting to etcd running on CoreOS.

from python-etcd.

The library is tested with 0.4.6 and failure to write while you can still read means your etcd cluster has lost quorum, most probably.

from python-etcd.