** Changed in: maas
Status: Fix Committed => Fix Released
--
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:
Fix Released
Status in MAAS 2.3 series:
Triaged
Status in MAAS 2.4 series:
Triaged
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
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
