Netplan does not apply at boot after upgrade to 20.04

[Lithi]

Upgraded from 18.04 to 20.04 and now when the system boots Netplan fails to configure the interface. After booting I must run 'netplan apply' for the interface to be brought up.

Here is my /etc/netplan/01-netcfg.yaml

network:
  version: 2
  renderer: networkd
  ethernets:
    eno1:
      dhcp4: no
      dhcp6: no
  bridges:
    br0:
      dhcp4: no
      interfaces:
        - eno1
      addresses: [192.168.0.10/24]
      gateway4: 192.168.0.1
      nameservers:
        addresses: [192.168.0.1]
      parameters:
        stp: false
        forward-delay: 0
~

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: netplan.io 0.99-0ubuntu3~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Tue May 19 18:02:15 2020
SourcePackage: netplan.io
UpgradeStatus: Upgraded to focal on 2020-04-25 (24 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jim Pye (jimpye)]

In my instance it was a fresh install of 20.04 LTS.

Work around is to specify the MAC address (macaddress:) option on the Bridge definition.

.
.
.
bridges:
  br0:
    interfaces:
      - eno1
    macaddress: xx:xx:xx:xx:xx:xx
    dhcp4: no
.
.
.

I also have the match and macaddress options in the eno1 stanza, but not sure if this actually needed.

Note the macaddress I have used is the real MAC address of the NIC.

HTH
Jim

[Lukas Märdian (slyon)]

Hi,
could you please report the systemd version you're using?

# dpkg -l | grep systemd

It might be a duplicate of https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1860926 and thus be fixed in systemd 242-7ubuntu3.9

[Lithi (lithi)]

Hi,

systemd 245.4-4ubuntu3.1

Thank you for the updated info!

[Jim Pye (jimpye)]

Mine reports the same version as Lithi:

ii networkd-dispatcher 2.0.1-1 all Dispatcher service for systemd-networkd connection status changes
ii systemd 245.4-4ubuntu3.1 amd64 system and service manager

Cheers
Jim

[Dan Streetman (ddstreet)]

@lithi @jimpye have you rebooted since upgrading systemd to version ...ubuntu3.1? (to verify the problem still happens)

[Jim Pye (jimpye)]

For me the machine I installed 20.04 on is a host for Virtual Machines and I have installed Livepatch on to minimise the reboots. :)

I will have a look at testing this on a VM on this machine and get back.

[Jim Pye (jimpye)]

@ddstreet

I have rebooted both a VM and the original machine without my work around of the macaddress option in the bridge configuration and they are both now working on the reboot.

I can see from the apt/history.log that between first reporting this issue and now, the systemd:amd64 package was updated:

Start-Date: 2020-05-27 17:36:34
Commandline: apt-get dist-upgrade
Requested-By: user (1000)
Upgrade: libsystemd0:amd64 (245.4-4ubuntu3, 245.4-4ubuntu3.1), ubuntu-standard:amd64 (1.450, 1.450.1), udev:amd64 (245.4-4ubuntu3, 245.4-4ubuntu3.1), ubuntu-server:amd64 (1.450, 1.450.1), libnss-mymachines:amd64 (245.4-4ubuntu3, 245.4-4ubuntu3.1), libudev1:amd64 (245.4-4ubuntu3, 245.4-4ubuntu3.1), systemd-timesyncd:amd64 (245.4-4ubuntu3, 245.4-4ubuntu3.1), ubuntu-minimal:amd64 (1.450, 1.450.1), systemd-sysv:amd64 (245.4-4ubuntu3, 245.4-4ubuntu3.1), libpam-systemd:amd64 (245.4-4ubuntu3, 245.4-4ubuntu3.1), systemd:amd64 (245.4-4ubuntu3, 245.4-4ubuntu3.1), libnss-systemd:amd64 (245.4-4ubuntu3, 245.4-4ubuntu3.1), systemd-container:amd64 (245.4-4ubuntu3, 245.4-4ubuntu3.1)
End-Date: 2020-05-27 17:37:03

So for me this issue has now been resolved.

Thanks for your efforts
Jim