bionic: static maas missing search domain in systemd-resolve configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Eric Claude Jones | ||
2.3 |
Fix Released
|
High
|
Eric Claude Jones | ||
MAAS |
Fix Released
|
Medium
|
Mike Pontillo | ||
cloud-init |
Won't Fix
|
Undecided
|
Unassigned |
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:/
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@
node-name.maas has address 10.245.168.0
Related branches
- Andres Rodriguez (community): Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 162 lines (+32/-18)2 files modifiedsrc/maasserver/preseed_network.py (+11/-7)
src/maasserver/tests/test_preseed_network.py (+21/-11)
summary: |
- bionic: lxd containers missing search domain in systemd-resolve + bionic: manual maas missing search domain in systemd-resolve configuration |
summary: |
- bionic: manual maas missing search domain in systemd-resolve + bionic: static maas missing search domain in systemd-resolve configuration |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Changed in maas: | |
assignee: | nobody → Mike Pontillo (mpontillo) |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
milestone: | 2.5.0 → 2.5.0alpha1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
no longer affects: | maas/2.3 |
no longer affects: | maas/2.4 |
A interesting twist on this is that juju seems to do the right thing when host system is xenial and container is bionic (See below).
It may be that this is a generic issue at some level on Ubuntu after move to systemd-resolve. Other interesting bugs I have found on the subject: /bugs.launchpad .net/ubuntu/ +source/ network- manager/ +bug/1684854 /github. com/systemd/ systemd/ issues/ 6572
https:/
https:/
Excerpt of test displaying this working for juju deployed bionic container on xenial host system (all hosts are in the .maas domain and pinging by just using hostname part works. Repeating this test with Bionic as host system will fail):
$ juju status
Model Controller Cloud/Region Version SLA
default maas maas 2.4-rc1 unsupported
App Version Status Scale Charm Store Rev OS Notes
Unit Workload Agent Machine Public address Ports Message
Machine State DNS Inst id Series AZ Message
0 started 172.16.122.251 qkm377 xenial default Deployed
0/lxd/0 started 172.16.122.253 juju-4d3dd7-0-lxd-0 xenial default Container started
0/lxd/1 started 172.16.122.252 juju-4d3dd7-0-lxd-1 bionic default Container started
Controller Timestamp
15 May 2018 15:23:46+02:00
$ juju ssh 0 'lsb_release -a &&ping -c 1 awake-yak'
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.4 LTS
Release: 16.04
Codename: xenial
PING awake-yak.maas (172.16.122.250) 56(84) bytes of data.
64 bytes from awake-yak.maas (172.16.122.250): icmp_seq=1 ttl=64 time=0.319 ms
--- awake-yak.maas ping statistics --- 319/0.319/ 0.000 ms
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.319/0.
Connection to 172.16.122.251 closed.
$ juju ssh 0/lxd/0 'lsb_release -a &&ping -c 1 awake-yak'
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.4 LTS
Release: 16.04
Codename: xenial
PING awake-yak.maas (172.16.122.250) 56(84) bytes of data.
64 bytes from awake-yak.maas (172.16.122.250): icmp_seq=1 ttl=64 time=0.205 ms
--- awake-yak.maas ping statistics --- 205/0.205/ 0.000 ms
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.205/0.
Connection to 172.16.122.253 closed.
$ juju ssh 0/lxd/1 'lsb_release -a &&ping -c 1 awake-yak'
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04 LTS
Release: 18.04
Codename: bionic
PING awake-yak.maas (172.16.122.250) 56(84) bytes of data.
64 bytes from awake-yak.maas (172.16.122.250): icmp_seq=1 ttl=64 time=0.116 ms
--- awake-yak.maas ping statistics --- 116/0.116/ 0.000 ms
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.116/0.
Connection to 172.16.122.252 closed.