It sounds like we are failing to find the search domain and add it to the
configuration.

John
=:->

On Thu, May 24, 2018, 20:40 Alex Kavanagh <email address hidden>
wrote:

> So here is the information that hopefully will be useful.
>
> 1. /etc/netplan/99-juju.yaml on the container:
>
> network:
>   version: 2
>   ethernets:
>     eth0:
>       match:
>         macaddress: 00:16:3e:d0:b4:4e
>       addresses:
>       - 10.245.168.48/21
>       gateway4: 10.245.168.1
>       nameservers:
>         addresses: [10.245.168.6]
>
> 2. host machine's /etc/resolve.conf:
>
> # This file is managed by man:systemd-resolved(8). Do not edit.
> #
> ...
> #
> # See man:systemd-resolved.service(8) for details about the supported
> modes of
> # operation for /etc/resolv.conf.
>
> 3. nameserver 127.0.0.53
>
> 4. juju debug-log --replay --include-module juju.provisioner
> machine-1: 15:34:02 WARNING juju.provisioner incomplete DNS config found,
> discovering host's DNS config
> machine-2: 15:34:30 WARNING juju.provisioner incomplete DNS config found,
> discovering host's DNS config
> machine-2: 15:34:39 WARNING juju.provisioner incomplete DNS config found,
> discovering host's DNS config
> machine-2: 15:34:44 WARNING juju.provisioner failed to start machine
> 2/lxd/2 (failed to ensure LXD image: Failed remote image download: UNIQUE
> constraint failed: images_aliases.name), retrying in 10s (10 more
> attempts)
> machine-2: 15:34:57 WARNING juju.provisioner incomplete DNS config found,
> discovering host's DNS config
> machine-0: 15:35:08 WARNING juju.provisioner incomplete DNS config found,
> discovering host's DNS config
> machine-0: 15:35:16 WARNING juju.provisioner incomplete DNS config found,
> discovering host's DNS config
> machine-0: 15:35:22 WARNING juju.provisioner failed to start machine
> 0/lxd/2 (failed to ensure LXD image: Failed remote image download: UNIQUE
> constraint failed: images_aliases.name), retrying in 10s (10 more
> attempts)
> machine-0: 15:35:37 WARNING juju.provisioner incomplete DNS config found,
> discovering host's DNS config
> machine-3: 15:35:52 WARNING juju.provisioner incomplete DNS config found,
> discovering host's DNS config
> machine-0: 15:36:41 WARNING juju.provisioner incomplete DNS config found,
> discovering host's DNS config
> machine-1: 15:39:26 WARNING juju.provisioner incomplete DNS config found,
> discovering host's DNS config
> machine-3: 15:40:57 WARNING juju.provisioner incomplete DNS config found,
> discovering host's DNS config
> machine-3: 15:41:22 WARNING juju.provisioner incomplete DNS config found,
> discovering host's DNS config
> machine-2: 15:42:53 WARNING juju.provisioner incomplete DNS config found,
> discovering host's DNS config
>
> So, yes, lots of "incomplete DNS config found" lines (I think one per
> container).
>
> 5. juju debug-log -m controller --replay --include-module juju.provisioner
> machine-0: 15:12:49 INFO juju.provisioner provisioner-harvest-mode is set
> to destroyed; unknown instances not stopped []
>
> 6. juju --version
> 2.4-beta3-xenial-amd64  (actually from snap: 2.4-beta3+develop-c17354d
>
> 7. The container and host does resolve; it's just that there is no
> search domain so nova-cloud-controller fails:  See
> https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1765405
>
> Add a search domain (maas) to the netplan config and applying it then
> allows nova-cloud-controller to work.
>
> --
>
>
> I've left the system up; if there are any more details you would like then
> please let me know.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1771885
>
> Title:
>   bionic: lxd containers missing search domain in systemd-resolve
>   configuration
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1771885/+subscriptions
>