[Bug 1114098] New: fedora 20: etcd broken on install, very out of date, and misconfigured.

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1114098

            Bug ID: 1114098
           Summary: fedora 20: etcd broken on install, very out of date,
                    and misconfigured.
           Product: Fedora
           Version: 20
         Component: etcd
          Assignee: lacypret(a)gmail.com
          Reporter: bugs(a)jameskyle.org
        QA Contact: extras-qa(a)fedoraproject.org
                CC: golang(a)lists.fedoraproject.org, lacypret(a)gmail.com,
                    lemenkov(a)gmail.com



Description of problem:

etcd service on fedora 20 only returns 404 page not found for all queries.

Version-Release number of selected component (if applicable):

Fedora 20, etcd 0.1.3

How reproducible:

100%

Steps to Reproduce:
1. yum install etcd
2. systemctl start etcd
3. curl http://127.0.0.1:4001/v2/keys/foo -d "Bar"

Actual results:

404 page not found

Expected results:

{"action":"set","node":{"key":"/message","value":"Hello","modifiedIndex":5,"createdIndex":5}}

Additional info:

The service was configured to use a systemd socket service, but (from the
systemd debs) "etcd doesn't have socket activation".

Even if I disabled the socket service and ran etcd 0.1.3 in the foreground with
defaults, the same behavior was manifest. 

Installing the current 0.4.4 version of etcd produced the expected/desired
behavior.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 1114098] fedora 20: etcd broken on install, very out of date, and misconfigured.

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1114098

Peter Lemenkov <lemenkov(a)gmail.com&gt; changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
         Resolution|---                         |CURRENTRELEASE
        Last Closed|                            |2014-12-19 09:16:56



--- Comment #1 from Peter Lemenkov <lemenkov(a)gmail.com&gt; ---
Fixed already.

-- 
You are receiving this mail because:
You are on the CC list for the bug.