Thanks for the feedback! So it seems to be a race condition between a systemd "daemon-reload" (triggering the Netplan generator) and starting of NetworkManager.
We have a (partial?) reproducer in comment #11, but it's still unclear to me how the 12/24 h warm-reboot tests are being triggered. We have a workaround in comment #9. I think the core issue is that the Netplan generator should not re-write the NM configuration during daemon-reload and there's some pending work upstream of refactoring the Netplan generator accordingly: https://github.com/canonical/netplan/pull/552 ** Changed in: netplan.io (Ubuntu) Status: Incomplete => Triaged ** Changed in: netplan.io (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083129 Title: [Lenovo Ubuntu 22.04.4 Bug] netplan static IP address assignment use NetworkManager as renderer would be lost static ip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2083129/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
