I did get this suggestion from someone internally: +++ That one line in there about unmanaged devices reminds me of this old thing https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842 -- loads of people found our /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf configuration causing problems managing wired interfaces, or something like that. i'm not sure why it would be non-deterministic though :(
I think my hunch could be tested via the comment #6 workaround `touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf` +++ So see if the comment 6 workaround in that bug helps... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2083129 Title: [Lenovo Ubuntu 24.04.4 Bug] netplan static IP address assignment use NetworkManager as renderer would be lost static ip Status in network-manager package in Ubuntu: New Bug description: On Ubuntu 22.04.4, to configure a system to use static address assignment, create a netplan configuration in the file, like /etc/netplan/00-installer-config.yaml. After assigning the network configuration abstraction renderer to NetworkManager not networkd in /etc/netplan/00-installer-config.yaml, then we do warm reboot test, some of the NIC interface lost their static ip in some reboot cycles when the rendered is NetworkManager, but networkd as a renderer is works well, all NIC interfaces can get their corresponding IP that configured in netplan confile file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2083129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
