Thanks for going through the extra steps to track down the issue.
John
=:->
On Thu, May 17, 2018, 20:11 Joseph Phillips <email address hidden>
wrote:
> This issue remains if the following sequence is followed:
>
> - Bootstrap.
> - Add a machine.
> - SSH onto the new machine and install LXD from backports.
> - Deploy to, or create a new container on the machine.
>
> This should be rectified by ensuring IPv4 config when interrogating the
> default bridge.
>
> ** Changed in: juju
> Status: Fix Committed => In Progress
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1668547
>
> Title:
> juju doesn't configure lxdbr0 properly with new LXD (>2.3)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1668547/+subscriptions
>
Thanks for going through the extra steps to track down the issue.
John
=:->
On Thu, May 17, 2018, 20:11 Joseph Phillips <email address hidden>
wrote:
> This issue remains if the following sequence is followed: /bugs.launchpad .net/bugs/ 1668547 /bugs.launchpad .net/juju/ +bug/1668547/ +subscriptions
>
> - Bootstrap.
> - Add a machine.
> - SSH onto the new machine and install LXD from backports.
> - Deploy to, or create a new container on the machine.
>
> This should be rectified by ensuring IPv4 config when interrogating the
> default bridge.
>
> ** Changed in: juju
> Status: Fix Committed => In Progress
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> juju doesn't configure lxdbr0 properly with new LXD (>2.3)
>
> To manage notifications about this bug go to:
> https:/
>