Comment 2 for bug 2039436

The peer-grouper worker, which maintains the MongoDB cluster needs to identify a unique local-cloud scoped address to which MongoDB is bound.

Where multiple are available, the one to use is specified by supplying config for the juju-ha-space.

This could be made to work on MAAS, where the subnets/spaces are provider-sourced, and therefore known at model creation.

However this is not the case with the manual provider, as there are no space definitions.

As part of the Juju 4.0 work we are moving some of this behaviour to the controller charm itself, so we will endeavour to accommodate this scenario.

Until that time, the stated work-around is the avenue to take.