Comment 4 for bug 1468579

@lmic: can you explain how the above output was obtained? It looks like a mix of "juju bootstrap --debug" output mixed in with cloud-init output and machine agent logs.

It's also curious that there's logs for jujud starting up twice. The first time Juju is able to connect to mongo fine, the second time it can't which is why MaybeInitiateMongoServer failed. Do you know why there's 2 jujud startups in this output?

Is the problem occurring consistently for you? If not, how many time have you seen it?

My best guess so far is that Juju is choosing the wrong address to connect to mongod with during bootstrap. I'm going to add some logging to 1.24 and 1.25 to help diagnose this. I can provide a pre-release build with this if you'd like to try it out before the releases are out.