wpa starts too late causing delay at boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
netplan |
Fix Released
|
Critical
|
Unassigned | ||
netplan.io (Ubuntu) |
Fix Released
|
Critical
|
Mathieu Trudel-Lapierre | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Devices which depend on a wireless network connection at boot.
[Test case]
1) Configure netplan with a single wireless network to be brought up:
network:
version: 2
renderer: networkd
wifis:
wlan0:
dhcp4: true
access-
home:
password: somepassword
2) Reboot the device.
3) Check how long the device takes to boot and come up to a login prompt.
4) Check the output of 'systemd-analyze critical-chain' and 'systemd-analyze blame'. The time required for netplan-wpa@ and systemd-
[Regression potential]
As this changes timing and ordering for the boot-time services, pay particular attention to any issues that come up as delay at booting caused by systemd-
---
Especially on raspberry pis, the wpa service set up by netplan when wifi is configured is enabled far too late in the boot order, causing unnecessary delays.
There's a visible delay of upwards to 2 minutes at booting a rpi3 with netplan.io 0.95 as it is in disco; testing with a patched version shows this delay can be completely eliminated by fixing the netplan-wpa service and setting DefaultDependen
Changed in netplan.io (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Critical |
assignee: | nobody → Mathieu Trudel-Lapierre (cyphermox) |
Changed in netplan: | |
importance: | Undecided → Critical |
status: | New → Fix Released |
This has been fixed upstream as https:/ /github. com/CanonicalLt d/netplan/ commit/ ffda192123b4de0 c1f270767c3334d 75ef2ebcc1