systemd-networkd-wait-online & two ethernet on board

[Radek Secka]

Since I've upgraded to 19.04 my boot was 3 minutes longer due to wait for network. I've tried many tricks, but today I have finally found the source = the bug.
My PC has motherboard AsRock Z370M-ITX/ac which has 2 Ethernet ports. When I connect Ethernet cable just to the "first" device "enp3s0" boot is quick, when I connect Ethernet cable just to the "second" device "enp0s31f6" boot is about 3 minutes longer.

It simply waits for the "enp3s0" device.

Since there is no mark on the board or on the rear panel which port is "first" and which is "second" it's clear that the failure is on Ubuntu 19.04 side. Ubuntu 18.04 LTS has no such problem.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: systemd 240-6ubuntu5.3
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Aug 15 21:55:12 2019
InstallationDate: Installed on 2017-12-22 (600 days ago)
InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=d383d414-f179-4df7-a8f3-890dacf8ca33 ro modprobe.blacklist=nouveau intel_iommu=on
SourcePackage: systemd
UpgradeStatus: Upgraded to disco on 2019-06-22 (54 days ago)
dmi.bios.date: 03/21/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.10
dmi.board.name: Z370M-ITX/ac
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd03/21/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ370M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Kai-Heng Feng (kaihengfeng)]

Do they have same MAC address?

[Dan Streetman (ddstreet)]

what's your network configuration? are you using netplan? or network-manager? or have you configured systemd-networkd manually?

[Radek Secka (atho)]

No they don't have same MAC but the difference is just one bit.

I'm using network-manager and I didn't changed systemd-networkd configuration manually.
May be it was changed during Upgrade LTS 18.04 -> 19.04

[Dan Streetman (ddstreet)]

can you attach your syslog? As well as any files you find in:
/etc/netplan/
/etc/systemd/network/
/run/systemd/network/

[Radek Secka (atho)]

In syslog was just:
systemd-networkd-wait-online[4903]: Event loop failed: Connection timed out
apt-helper[4892]: E: Sub-process /lib/systemd/systemd-networkd-wait-online returned an error code (1)

In /etc/netplan/ just 01-netcfg.yaml (Attachment)
/etc/systemd/network is empty
In /run/systemd/network/ just 10-netplatn-enp3s0.network (Attachment)

[Dan Streetman (ddstreet)]

Your netplan config has enp3s0 as your main interface, and by default that is required for boot, which is why your boot is delayed when you don't have it connected.

Change your netplan 01-netcfg.yaml file to:

# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
  version: 2
  renderer: networkd
  ethernets:
    enp3s0:
      dhcp4: yes
      optional: yes
    enp0s31f6:
      dhcp4: yes
      optional: yes

that should start dhcp4 on both your ethernet ports, but also won't delay your boot. See the netplan man page for more details about its config params.

[Launchpad Janitor (janitor)]

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