Comment 4 for bug 1843497

Do you know if this cluster ran etcd 2.3 at any point in the past?

What version of etcd is it running now? (see Version column in `juju status` output)

Right now it looks like I can reproduce this if I start with etcd 2.3, migrate to etcd 3.0, and then upgrade the etcd charm from rev 431 to 449. Doing that put all my units in an "Errored with 0 known peers" state with symptoms similar to those described in the bug description. I have so far been unable to produce any errors if I start the deployment with etcd 3.0 or 3.2 instead.