Comment 7 for bug 1764317

There are several bionic related issues that should be fixed and released
to 2.3.8

John
=:->

On Mon, May 7, 2018, 18:01 KingJ <email address hidden> wrote:

> Although a fix has now been merged in to the development branch, is
> there any way to apply the workaround on the current stable release
> other than SSHing in to every container and modifying/applying the
> netplan configuration? I'm currently using Juju with MAAS to roll out an
> OpenStack cluster and with the number of services that use LXD there's
> quite a few things to change.
>
> Right now the least resource intensive way i've found to apply the
> change is to run this for each app;
>
> juju run "sed -i 's/127.0.0.53/10.1.10.1/' /etc/netplan/99-juju.yaml;
> netplan apply" --application=openstack-dashboard
>
> --
> You received this bug notification because you are a member of Canonical
> Field High, which is subscribed to the bug report.
> https://bugs.launchpad.net/bugs/1764317
>
> Title:
> bionic LXD containers on bionic hosts get incorrect /etc/resolve.conf
> files
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1764317/+subscriptions
>