Comment 1 for bug 1829513

If things are happy otherwise, I have the feeling this is an issue around
"we list all the IPs, but they only need a subset of them", and then they
issue warnings when some of those addresses don't actually work. (eg, we
ask to connect on both public and private, but only private succeeds, but
you end up with warnings about the public ones, even though we don't need
them.)
The list of addresses to connect to Mongo (by the driver) aren't updatable
while connected (so you also run into warnings when one controller goes
down, you bring up another, but otherwise the connection remains stable.)
It might be interesting if we split the connection information so that you
had one logical unit of Mongod with multiple plausible IPs, and you
wouldn't warn as long as you were connected to one of those IPs (and we'd
want a way to update that list on an existing connection.)

On Wed, May 22, 2019 at 3:50 AM Tim Penhey <email address hidden> wrote:

> ** Tags added: canonical-is gce-provider
>
> ** Changed in: juju
> Status: New => Triaged
>
> ** Changed in: juju
> Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1829513
>
> Title:
> GCE controllers trying to connect to mongodb using the public IP
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1829513/+subscriptions
>