[Bug 1734409] Update Released
Ćukasz Zemczak
1734409 at bugs.launchpad.net
Wed Mar 21 11:53:59 UTC 2018
The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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 Released
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
More information about the foundations-bugs
mailing list