Comment 2 for bug 1931961

This is due to:
- https://bugs.launchpad.net/juju-core/+bug/1416928
- https://bugs.launchpad.net/juju/+bug/1567683

These were addressed by filtering lxdbr0 from API server addresses, as seen in this log output:

machine-0: 10:34:09 DEBUG juju.network filtering "lxdbr0" address local-cloud:10.78.171.220 for machine
machine-0: 10:34:09 DEBUG juju.network including address local-machine:127.0.0.1 for machine
machine-0: 10:34:09 DEBUG juju.network including address local-machine:::1 for machine
machine-0: 10:34:09 DEBUG juju.network addresses after filtering: [local-machine:127.0.0.1 local-machine:::1]
machine-0: 10:34:09 DEBUG juju.worker.apiaddressupdater updating API hostPorts to [[127.0.0.1:17070 [::1]:17070]]
machine-0: 10:34:09 DEBUG juju.agent API server address details [["127.0.0.1:17070" "[::1]:17070"]] written to agent config as []

A work-around that should work is to create a bridge with a different name and use that during "lxd init".

I'll mark as incomplete for now; waiting to hear if an alternative bridge setup works.