To be clear, that carrier is set to "failed" when retriggering uevents is not the main problem. The main problem is that after 5-10 minutes, networkd silently takes control again of the ethernet interface. The retriggering of uevents and the reaction on the networkd side is just an indication that it still cares about the interface.
Maybe a better way to check if the issue is around without having to wait for minutes would be to look at /run/systemd/netif/links/* and check if the content still references the removed .network files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058976 Title: Configuration files for networkd are created when NetworkManager is the default renderer To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2058976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
