After upgrading several 22.04 servers to 24.04, the NetworkManager
connection files were automatically migrated to netplan, and new
connections automatically go to /etc/netplan.

Some of the issues I've seen:

1) Forced UUID based file names:
Previously, I would edit 
/etc/NetworkMananger/system-connections/vlan31.nmconnection.
Now I need to edit /etc/netplan/90-NM-37a0bb34-7f68-32a0-0002-000000000031.yaml.
I can't have normal file names anymore; I need to grep through all my 
connections to locate it, and then copy/paste the resulting filename.

2) If I manually rename
/etc/netplan/90-NM-37a0bb34-7f68-32a0-0002-000000000031.yaml to
/etc/netplan/90-vlan31.yaml and reboot, and then use nmtui or the GUI to
edit the connection, I get yet another
90-NM-37a0bb34-7f68-32a0-0002-000000000031.yaml file. Now I have two
files.

3) Confusing contents. For example, that VLAN connection contains:
network:
version: 2
vlans:
enp1s0.31:
renderer: NetworkManager
addresses:
- "1.2.3.4/29"
...
networkmanager:
uuid: "37a0bb34-7f68-32a0-0002-000000000031"
name: "VLAN31"
passthrough:
connection.timestamp: "1726302619"
ethernet._: ""
vlan.flags: "1"
ipv4.address1: "1.2.3.4/29,1.2.3.1"

So for example, if I need to change the IP, I need to change it twice,
once under "addresses" and once under "passthrough".

4) Badly mapped content.
In the example above, I have:
vlans:
enp1s0.31:
While in Network Manager I didn't need to specify the interface name. If I 
replaced my network card e.g. from enp1s0 to enp2s0, the VLAN would 
automatically be named enp2s0.31. Now if I delete the VLAN interface name from 
the NetworkManager text box and save the connection, it's not deleted like it 
should.

These are from the first days of use, I'm sure there will be more issues
if we keep using this backend.

Please do add a configuration option to avoid the yaml NM backend. The
compilation time option isn't appropriate, we shouldn't be risking to
lose all security updates because of local compilation of packages.
Thank you!

(and if someone creates a PPA with an un-patched network manager to be
able to function until this issue is properly resolved, please notify us
in this topic :))

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2041491

Title:
  Provide an option to avoid the yaml NM backend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041491/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to