netplan apply doesn't activate NetworkManager
Bug #1789130 reported by
Mason Loring Bliss
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
netplan.io (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Starting with the Ubuntu Server install, I get netplan driving systemd-networkd by default.
If I change /etc/netplan/
Attached screenshot illustrates what I see.
Changed in netplan.io (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
To post a comment you must log in.
I just tried again on a fresh install, and noted this in syslog:
Aug 27 21:55:14 penguin systemd- timesyncd[ 904]: Network configuration changed, trying to establish connection. rfkill[ 9744]: Failed to open device rfkill0: No such device timesyncd[ 904]: Synchronized to time server 91.189.91.157:123 (ntp.ubuntu.com). IWLWIFI_ DEBUG disabled IWLWIFI_ DEBUGFS enabled IWLWIFI_ DEVICE_ TRACING enabled udevd[9759] : link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. networkd[ 922]: wlan0: Interface name change detected, wlan0 has been renamed to wlp3s0. timesyncd[ 904]: Network configuration changed, trying to establish connection. dispatcher[ 1123]: WARNING:Unknown index 4 seen, reloading interface list timesyncd[ 904]: Synchronized to time server 91.189.91.157:123 (ntp.ubuntu.com). pci0000: 00/0000: 00:1c.1/ 0000:03: 00.0': not supported by any plugin
Aug 27 21:55:14 penguin systemd[1]: Starting Load/Save RF Kill Switch Status...
Aug 27 21:55:14 penguin systemd-
Aug 27 21:55:14 penguin systemd[1]: Started Load/Save RF Kill Switch Status.
Aug 27 21:55:14 penguin systemd-
Aug 27 21:55:14 penguin kernel: [24668.459650] iwlwifi 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
Aug 27 21:55:14 penguin kernel: [24668.460729] iwlwifi 0000:03:00.0: loaded firmware version 18.168.6.1 op_mode iwldvm
Aug 27 21:55:14 penguin kernel: [24668.460758] iwlwifi 0000:03:00.0: CONFIG_
Aug 27 21:55:14 penguin kernel: [24668.460760] iwlwifi 0000:03:00.0: CONFIG_
Aug 27 21:55:14 penguin kernel: [24668.460761] iwlwifi 0000:03:00.0: CONFIG_
Aug 27 21:55:14 penguin kernel: [24668.460764] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Advanced-N 6205 AGN, REV=0xB0
Aug 27 21:55:14 penguin kernel: [24668.489358] ieee80211 phy1: Selected rate control algorithm 'iwl-agn-rs'
Aug 27 21:55:14 penguin systemd-
Aug 27 21:55:14 penguin kernel: [24668.492733] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
Aug 27 21:55:14 penguin systemd-
Aug 27 21:55:14 penguin systemd-
Aug 27 21:55:14 penguin networkd-
Aug 27 21:55:14 penguin systemd-
Aug 27 21:55:17 penguin ModemManager[9578]: <info> Couldn't check support for device at '/sys/devices/
That said, if I manually start NetworkManager afterwards, it appears to inherit network handling unproblematically without a reboot.