Comment 5 for bug 1728111

tl;dr leadership changed during the seeding of the passwords (so between a call to is-leader and leader-set) which the charm does not currently deal with so the cluster never bootstrapped.

I'm guessing this is not that easy to reproduce but at least the cause is visible from the log data provided; the logs from the controller might tell is more about why leadership changed.