Intermittent DHCP startup failure during boot due to potential race condition in interface renaming
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Focal |
New
|
Undecided
|
Unassigned |
Bug Description
The server fails to start its network with DHCP seemingly randomly. It can take a few reboots to bring up the network. This causes issues where automated updates that trigger a reboot cause the server to go offline.
I've attached syslog examples of both success and failure.
My assumption is that the cause of this bug is a race condition where systemd is not waiting on the interface renaming.
Notably, when it boots properly, it says:
"Interface is under renaming, pending initialization."
That message is not logged when it fails.
The server uses cloud-init, and the cloud image provided by Ubuntu.
Another possible explanation is the netplan configuration at /etc/netplan/
network:
version: 2
ethernets:
eth0:
dhcp4: true
match:
Maybe set-name is redundant here, but it's the default configuration generated by cloud-init.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.21
ProcVersionSign
Uname: Linux 5.4.0-164-generic x86_64
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
Date: Wed Oct 18 16:22:57 2023
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
MachineType: Slicie.com Slicie Cloud Server
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=C.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.13.0-1ubuntu1.1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.
dmi.modalias: dmi:bvnSeaBIOS:
dmi.product.name: Slicie Cloud Server
dmi.product.
dmi.sys.vendor: Slicie.com