The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| netplan |
Invalid
|
Medium
|
Unassigned | ||
| network-manager (Ubuntu) |
Fix Released
|
Undecided
|
Lukas Märdian | ||
Bug Description
Steps to reproduce:
1. Install Ubuntu Lunar or a flavor thereof onto physical hardware with a WiFi adapter. (I used Lubuntu Lunar.)
2. Connect to WiFi and install all updates.
3. Enable the Netplan Everywhere PPA and install the updated NetworkManager from it (further details at https:/
4. When the installation finishes, run "sudo netplan get".
Expected result: Networking information related to the WiFi connection should appear in the "sudo netplan get" output.
Actual result: "sudo netplan get" returns the following:
** (process:4088): WARNING **: 12:41:41.394; Permissions for /etc/netplan/
network:
version: 2
renderer: NetworkManager
End of output. Additionally, the /etc/netplan folder does not contain files that I would expect to be there that would contain the networking info.
Additional information:
If I disconnect from WiFi, then delete my WiFi connection entirely in nmtui, and *then* reconnect to the same WiFi network, "sudo netplan get" returns the expected networking information. /etc/netplan is also properly populated after doing this.
This bug seems like it will probably cause unintended behavior after an upgrade from 23.04 (which uses normal NetworkManager) to 23.10 (which is supposed to be using the Netplan Everywhere NetworkManager). People probably won't know to entirely delete the WiFi and other connections and then reconnect them in order for the netplan output to be usable.
Related branches
- Simon Chopin: Needs Information
- Danilo Egea Gondolfo: Pending requested
-
Diff: 35 lines (+27/-0)1 file modifieddebian/network-manager.postinst (+27/-0)
- Sebastien Bacher: Approve
- Danilo Egea Gondolfo (community): Approve
- Lukas Märdian: Abstain
-
Diff: 1558 lines (+1454/-1)11 files modifieddebian/changelog (+14/-0)
debian/control (+4/-0)
debian/network-manager.postinst (+33/-0)
debian/network-manager.preinst (+18/-0)
debian/patches/netplan/0001-netplan-Adopt-buildsystems-for-Netplan-integration.patch (+134/-0)
debian/patches/netplan/0002-netplan-make-use-of-libnetplan-for-YAML-backend.patch (+525/-0)
debian/patches/series (+2/-0)
debian/rules (+2/-1)
debian/tests/control (+4/-0)
debian/tests/nm.py (+1/-0)
debian/tests/nm_netplan.py (+717/-0)
| description: | updated |
| description: | updated |
| Lukas Märdian (slyon) wrote | #1 |
| Changed in netplan: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: netplan-everywhere |
| Lukas Märdian (slyon) wrote | #2 |
| Changed in network-manager (Ubuntu): | |
| status: | New → In Progress |
| assignee: | nobody → Lukas Märdian (slyon) |
| Lukas Märdian (slyon) wrote | #3 |
| Lukas Märdian (slyon) wrote | #4 |
| Changed in network-manager (Ubuntu): | |
| status: | In Progress → Fix Committed |
| Changed in netplan: | |
| status: | Triaged → Invalid |
| Changed in network-manager (Ubuntu): | |
| status: | Fix Committed → Fix Released |
| Simon Déziel (sdeziel) wrote | #5 |
| Lukas Märdian (slyon) wrote | #6 |
Hi Aaron, thank you very much for testing and spotting this "issue".
What you see is currently the "expected behavior", as described in https:/
I.e. connection profiles not being imported into /etc/netplan by default (on installation), but only once (re-)created or modified through NetworkManager.
But maybe it's not the way that users would intuitively expect it to be and the NetworkManager package should automatically re-create and import all current connection profiles from /etc/NetworkMan