Hello! We have a rather large environment with ~1500 computers and we keep hitting this issue annoyingly often. Is masking the systemd-networkd service unit a viable fix (that will not cascade onwards to cause new issues) for production systems or could the systemd patch be issued as an SRU to fix only the underlying bug (it looks like the SRU process was aborted for some reason)?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2028023 Title: [jammy] DNS issue triggered by command "udevadm trigger --subsystem- nomatch=input" To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2028023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
