Comment 5 for bug 2039126

As described, Juju cannot come up on manually provisioned machines that have multiple local-cloud scoped IP addresses.

This is due to the lease sub-system waiting for the peer-grouper worker to broadcast API addresses.

In turn this means that singular controller and model workers never start, and applications cannot achieve leader units.

3.2 uses Dqlite for leases and doesn't have the same issue. The peer-grouper worker will still keep logging errors, but the lease system doesn't rely on it and everything comes up as desired.

We do not intend to work on a fix for this in the earlier tracks.

A work-around is to use single-NIC machines for controllers, or disable all NICs but one prior to bootstrap, restoring them after.