Comment 9 for bug 1945225

Thanks for the investigation, I'm 100% +1 on comment #5.

The MR introduces some (low) risk of breaking existing use cases (#5.1), while not fixing the issue for anyone directly. Instead, it provides an (easier/additional?) workaround to the issue, which still needs to be applied to any individual machine hitting this issue.

So If there's any way to deploy the .link override configs, as suggested by @ddstreet, we should push for that instead of patching systemd. I would assume most deployment mechanisms (be it MAAS/cloud-init/...) should allow for placing additional udev config files. Worst case, it needs a reboot in between, I guess.

If anybody can prove that the .link override approach is not viable, we should ask the SRU team for their risk assesment of #5.1 and continue with the MR if they are +1 on it.