[Bug 1734409] Re: systemd-sysctl: exit gracefully on EPERM/EACCESS

[Brian Murray]

Hello Christian, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: systemd (Ubuntu Xenial)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

-- 
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 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