On thinking about this, it does seem the behavior change of udevadm will be highly disruptive to existing callers of udevadm trigger, so I opened upstream bug to try to address it without needing all callers to ignore its return code.
** Bug watch added: github.com/systemd/systemd/issues #13652 https://github.com/systemd/systemd/issues/13652 ** Also affects: systemd via https://github.com/systemd/systemd/issues/13652 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1845314 Title: udisks2 fails to install in a container with systemd 243 Status in systemd: Unknown Status in systemd package in Ubuntu: Confirmed Bug description: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1845314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
