Something similar got reported recently upstream, and I got a brand new discovery that one should actually call $ udevadm control --reload -> whenever configuration is changed, as upstream knows that all of their internal state caching and reloading is racy.
Could you please modify your reproducer test case to have: udevadm control --reload, before calling trigger action and check if this resolves your issue? If true, I believe netplan must call udevadm control --reload after writing out anything that udevd reads, which is udev .rules files and .link files. ** Also affects: nplan (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1669564 Title: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs