dns broken after upgrade to bionic

Bug #1771971 reported by karlsebal
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After upgrade to Bionic my DNS is broken. `resolv.conf` contains

```
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53
```

and network is configured via network manager and DHCP. But DNS will only work when entering the IP manually. Maybe something wrong with netplan?

```
~$ systemd-resolve --status
Global
          DNSSEC NTA: 10.in-addr.arpa
                      16.172.in-addr.arpa
                      168.192.in-addr.arpa
                      17.172.in-addr.arpa
                      18.172.in-addr.arpa
                      19.172.in-addr.arpa
                      20.172.in-addr.arpa
                      21.172.in-addr.arpa
                      22.172.in-addr.arpa
                      23.172.in-addr.arpa
                      24.172.in-addr.arpa
                      25.172.in-addr.arpa
                      26.172.in-addr.arpa
                      27.172.in-addr.arpa
                      28.172.in-addr.arpa
                      29.172.in-addr.arpa
                      30.172.in-addr.arpa
                      31.172.in-addr.arpa
                      corp
                      d.f.ip6.arpa
                      home
                      internal
                      intranet
                      lan
                      local
                      private
                      test

Link 3 (wlan0)
      Current Scopes: none
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no

Link 2 (eth0)
      Current Scopes: none
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no
```

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: netplan.io 0.36.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
Uname: Linux 4.15.0-20-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: i3
Date: Fri May 18 09:56:49 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-06-03 (1444 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: netplan.io
UpgradeStatus: Upgraded to bionic on 2018-05-13 (5 days ago)

Revision history for this message
karlsebal (karlsebal) wrote :
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

The attached files look exactly the way they should. Could you please also attach your netplan configuration?

If netplan specifies that the itnerface in managed by NetworkManager, we'll need to see if Networkmanager knows to add the DNS information to systemd-resolved.

Changed in netplan.io (Ubuntu):
status: New → Incomplete
Revision history for this message
karlsebal (karlsebal) wrote :

I am under the impression that there is no netplan config for `/etc/netplan` is empty.

Revision history for this message
karlsebal (karlsebal) wrote :

I created a config file `/etc/netplan/01-network-manager-all.yaml` and executed `netplan apply` but still no effect

```
$ cat /etc/netplan/01-network-manager-all.yaml
network:
  version: 2
  renderer: NetworkManager
```

Now I noticed that neplan seems to crash:

```
# systemctl status netplan
● netplan.service - LSB: Netplan calendar service.
   Loaded: loaded (/etc/init.d/netplan; generated)
   Active: active (exited) since Sun 2018-05-27 06:49:53 CEST; 14min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1397 ExecStart=/etc/init.d/netplan start (code=exited, status=

Mai 27 06:49:53 oz netplan[1397]:
Mai 27 06:49:53 oz netplan[1397]: help Show this help message
Mai 27 06:49:53 oz netplan[1397]: apply Apply current netplan con
Mai 27 06:49:53 oz netplan[1397]: generate Generate backend specific
Mai 27 06:49:53 oz netplan[1397]: /etc/netplan/*.yaml
Mai 27 06:49:53 oz netplan[1397]: ip Retrieve IP information f
Mai 27 06:49:53 oz netplan[1397]: try Try to apply a new netpla
Mai 27 06:49:53 oz netplan[1397]: automatic rollback
Mai 27 06:49:53 oz netplan[1397]: ...fail!
```

So I tried to execute the ExecStart command manually:

```
# /etc/init.d/netplan start
 * Starting plan appointment daemon netplan You need to specify a command
usage: /usr/sbin/netplan [-h] [--debug] ...

Network configuration in YAML

optional arguments:
  -h, --help show this help message and exit
  --debug Enable debug messages

Available commands:

    help Show this help message
    apply Apply current netplan config to running system
    generate Generate backend specific configuration files from
              /etc/netplan/*.yaml
    ip Retrieve IP information from the system
    try Try to apply a new netplan config to running system, with
              automatic rollback
                                                                  [fail]

```

Something wrong with that call it seems. Even more confusing: Systemd will not do anything when given the `start` command

```
# date +%T
07:10:47
# systemctl start netplan
# systemctl status netplan
● netplan.service - LSB: Netplan calendar service.
   Loaded: loaded (/etc/init.d/netplan; generated)
   Active: active (exited) since Sun 2018-05-27 06:49:53 CEST; 21min ago

```

Revision history for this message
karlsebal (karlsebal) wrote :

Once more with `--debug` enabled maybe this helps

```
# netplan --debug generate
DEBUG:command generate: running ['/lib/netplan/generate']
** (generate:3961): DEBUG: 07:16:07.718: Processing input file //etc/netplan/01-network-manager-all.yaml..
** (generate:3961): DEBUG: 07:16:07.718: starting new processing pass
** (generate:3961): DEBUG: 07:16:07.718: Generating output files..

# netplan --debug apply
** (generate:3964): DEBUG: 07:16:15.263: Processing input file //etc/netplan/01-network-manager-all.yaml..
** (generate:3964): DEBUG: 07:16:15.264: starting new processing pass
** (generate:3964): DEBUG: 07:16:15.264: Generating output files..
DEBUG:no netplan generated networkd configuration exists
DEBUG:no netplan generated NM configuration exists
DEBUG:replug eth0: unbinding 0000:02:00.0 from /sys/bus/pci/drivers/r8169
DEBUG:replug eth0: rebinding 0000:02:00.0 to /sys/bus/pci/drivers/r8169
DEBUG:device lo operstate is unknown, not replugging
DEBUG:netplan triggering .link rules for lo
DEBUG:device wlan0 operstate is up, not replugging
DEBUG:netplan triggering .link rules for wlan0
```

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

You seem to have a bad /etc/init.d/netplan file on the system; it's not coming from the netplan.io package. You should make sure you do not have the 'netplan' package installed (the network plan server).

Please attach the contents of /etc/NetworkManager/NetworkManager.conf.

affects: netplan.io (Ubuntu) → network-manager (Ubuntu)
Revision history for this message
karlsebal (karlsebal) wrote :

I purged `netplan` and `/etc/init.d/netplan` was removed. I reinstalled `netplan.io` but `/etc/init.d/netplan` now is missing completely. The nameserver however is now shown in `systemd-resolve --status` but still it does not work.

```
~# cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile,ofono
dns=dnsmasq

no-auto-default=E8:03:9A:F1:C2:6B,

[ifupdown]
managed=false
```

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in network-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.