root@systemd-sru-xenial:~# systemctl is-failed systemd-sysctl failed root@systemd-sru-xenial:~# dpkg-query -W systemd systemd 229-4ubuntu21.1
root@systemd-sru-xenial:~# dpkg-query -W systemd systemd 229-4ubuntu21.2 root@systemd-sru-xenial:~# systemctl restart systemd-sysctl root@systemd-sru-xenial:~# systemctl is-failed systemd-sysctl active ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- 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/1734409 Title: systemd-sysctl: exit gracefully on EPERM/EACCESS Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: [Impact] * systemd-sysctl service fails in containers, due to read-only sysfs, which is normal. [Test Case] * Ensure systemd-sysctl is successful in containers, e.g. lxc & lxd [Regression Potential] * The application of sysctls fails anyway, but at least in this case false-errors are not reported and the container doesn't enter "degraded" state without a good reason. [Other Info] * Original bug report Hi everyone, systemd-sysctl in systemd versions prior to 232 will exit with FAILED when not being able to apply kernel variables. In containers it should simply move on and exit with SUCCESS. Upstream systemd carries appropriate patches for this already. The relevant commits are: 411e869f497c7c7bd0688f1e3500f9043bc56e48 39540de8abe24886693ca29a9caeea85c88089aa these should be backported to xenial's systemd. Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734409/+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
