netplan-everywhere and existing wireguard connections
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Netplan |
Fix Released
|
High
|
Unassigned |
Bug Description
When creating a wireguard tunnel via Network Manager, a Netplan "nm-device" interface will be created with all the VPN information in the "networkmanager
The problem with that is that if you try to make any change to an existing wireguard tunnel connection that was created via Netplan, Network Manager will try to change its type from "tunnels" to "nm-devices" and libnetplan will fail:
Apr 17 09:23:03 yoga NetworkManager[
Apr 17 09:23:03 yoga NetworkManager[
Apr 17 09:23:03 yoga NetworkManager[
Apr 17 09:23:03 yoga NetworkManager[
In the example above I just tried to unset the connection "autoconnect" option in the GUI interface.
After that, any other change in any other connection will also crash Network Manager because it will try to persist the previous broken change.
In fact, if you have a WG tunnel in Netplan and try to install the network-
Error: failed to reload connections: GDBus.Error:
dpkg: error processing package network-manager (--configure):
installed network-manager package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of network-
network-
Package network-manager is not configured yet.
...
Related branches
- Lukas Märdian: Approve
- Sebastien Bacher: Pending requested
-
Diff: 514 lines (+317/-31)3 files modifieddebian/tests/control (+1/-1)
debian/tests/nm.py (+173/-20)
debian/tests/nm_netplan.py (+143/-10)
- Lukas Märdian: Approve
-
Diff: 106 lines (+63/-4)1 file modifieddebian/tests/nm_netplan.py (+63/-4)
Changed in netplan: | |
importance: | Undecided → High |
status: | New → Triaged |
Related to https:/ /bugs.launchpad .net/rochester/ +bug/1952967