yahoo-eng-team team mailing list archive

[Andres Rodriguez <andreserl@xxxxxxxxxxxxx>]

I'm re-opening this task for MAAS, as a user has been able to reproduce
this issue in a different context. While there's a work-around on
comment #22, the situation is that even when the same network
configuration sent for xenial and bionic deployments is the same, the
configuration differs, due to how cloud-init handles netplan
configuration.

More specifically, in Xenial, when MAAS sends DNS config for both
"global" and per-interface/subnet configuration, the resulting config is
that the machine will have an aggregation of the configuration for DNS.

However, when deploying Bionic, when MAAS sends the same exact
configuration, cloud-init interpret's it different and *only* the
network configuration of an interface is taken into consideration, while
the global is ignored.

As such, this *only* becomes an issue when the user overrides the DNS on
specific subnet, which results in the search domain not being considered
from the global config.

As such, we will make an improvement in MAAS to ensure that the search
domain is always included regardless.

** Changed in: maas
       Status: Invalid => New

** Changed in: maas
    Milestone: None => 2.5.0

** Also affects: maas/2.3
   Importance: Undecided
       Status: New

** Also affects: maas/2.4
   Importance: Undecided
       Status: New

** Changed in: maas/2.3
    Milestone: None => 2.4.1

** Changed in: maas/2.4
    Milestone: None => 2.3.4

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1771885

Title:
  bionic: static maas missing search domain in systemd-resolve
  configuration

Status in cloud-init:
  Won't Fix
Status in juju:
  Fix Released
Status in juju 2.3 series:
  Fix Released
Status in MAAS:
  New
Status in MAAS 2.3 series:
  New
Status in MAAS 2.4 series:
  New

Bug description:
  juju: 2.4-beta2  
  MAAS: 2.3.0

  Testing deployment of LXD containers on bionic (specifically for an
  openstack deployment) lead to this problem:

  https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1765405

  Summary:

  previously, the DNS config in the LXD containers were the same as the
  host machines

  now, the DNS config is in systemd, the DNS server is set correctly,
  but the search domain is missing, so hostnames won't resolve.

  Working resolv.conf on xenial lxd container:

  nameserver 10.245.168.6
  search maas

  Non-working "systemd-resolve --status":

  ...
  Link 21 (eth0)
        Current Scopes: DNS
         LLMNR setting: yes
  MulticastDNS setting: no
        DNSSEC setting: no
      DNSSEC supported: no
           DNS Servers: 10.245.168.6

  Working (now able to resolve hostnames after modifying netplan and
  adding search domain):

  Link 21 (eth0)
        Current Scopes: DNS
         LLMNR setting: yes
  MulticastDNS setting: no
        DNSSEC setting: no
      DNSSEC supported: no
           DNS Servers: 10.245.168.6
            DNS Domain: maas

  ubuntu@juju-6406ff-2-lxd-2:/etc$ host node-name
  node-name.maas has address 10.245.168.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1771885/+subscriptions