When a connection is deleted using any NM facility, libnetplan is failing to delete the YAML file. Because of that, the connection will be recreated when "netplan generate" runs again.
This is probably being caused by a combination of two things. First, the NM's systemd unit has this setting "ProtectSystem=true", which will mount /usr as read-only for NM. Second, we migrated the default "00-network-manager-all.yaml" file to, /usr/lib/netplan recently [1]. When libnetplan tries to open this file for writing, the open system fails with EROFS:
When a connection is deleted using any NM facility, libnetplan is failing to delete the YAML file. Because of that, the connection will be recreated when "netplan generate" runs again.
This is probably being caused by a combination of two things. First, the NM's systemd unit has this setting "ProtectSystem= true", which will mount /usr as read-only for NM. Second, we migrated the default "00-network- manager- all.yaml" file to, /usr/lib/netplan recently [1]. When libnetplan tries to open this file for writing, the open system fails with EROFS:
--- 00-network- manager- all.yaml" , O_WRONLY| O_CREAT| O_TRUNC, 0600) = -1 EROFS (Read-only file system) delete_ connection: Canno"..., 76) = 76
22517 openat(AT_FDCWD, "/lib/netplan/
22517 write(2, "netplan_
---
[1] - https:/ /launchpad. net/ubuntu/ +source/ ubuntu- settings/ 23.10.1