etcd follower sometimes comes up Errored with 0 known peers
Bug #1888729 reported by
George Kraft
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Etcd Charm |
Fix Released
|
High
|
George Kraft | ||
Bug Description
etcd/0* active idle 1 10.23.105.55 2379/tcp UnHealthy with 3 known peers
etcd/1 active idle 2 10.23.105.250 2379/tcp UnHealthy with 3 known peers
etcd/2 active idle 3 10.23.105.54 2379/tcp Errored with 0 known peers
This is blocking CI runs on s390x.
Revision history for this message
| George Kraft (cynerva) wrote | #1 |
| Changed in charm-etcd: | |
| importance: | Undecided → High |
| status: | New → In Progress |
| assignee: | nobody → George Kraft (cynerva) |
| Changed in charm-etcd: | |
| status: | In Progress → Fix Committed |
| tags: | removed: review-needed |
| Changed in charm-etcd: | |
| milestone: | none → 1.18+ck2 |
| tags: | added: backport-needed |
| Changed in charm-etcd: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I found this was occurring because the etcd/2 unit had re-rendered its etcd.conf.yml file, omitting the `cluster:` field, before etcd had completed registering.
Workaround:
juju run --unit etcd/2 -- charms.reactive clear_flag etcd.registered
juju run --unit etcd/2 -- hooks/update-status