systemd-sysctl in Xenial is not obeying the order of the sysctls
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| systemd (Ubuntu) |
Medium
|
Unassigned | ||
| Xenial |
Medium
|
Unassigned |
Bug Description
[Impact]
* sysctls are applied out of order
[Test Case]
* Monitor that sysctls are applied in-order, instead of out of order / random order.
[Regression Potential]
* Cherrypick of an upstream patch which is present in v232+ and in use in Ubuntu in later releases. The code changes are minimal, updating s/Hashmap/
https:/
[Other Info]
* Original bug report.
systemd-sysctl in Xenial forces itself over procps by shipping a link for procps.service to systemd-
Relevant upstream commit: https:/
Note that conf_files_
Philipp Kern (pkern) wrote : | #1 |
Changed in systemd (Ubuntu): | |
status: | New → Fix Released |
Changed in systemd (Ubuntu Xenial): | |
importance: | Undecided → Medium |
description: | updated |
Changed in systemd (Ubuntu Xenial): | |
status: | New → In Progress |
Hello Philipp, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
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-
Further information regarding the verification process can be found at https:/
Changed in systemd (Ubuntu Xenial): | |
status: | In Progress → Fix Committed |
tags: | added: verification-needed verification-needed-xenial |
Dimitri John Ledkov (xnox) wrote : | #3 |
Use multipass to launch a xenial VM with
$ dpkg-query -W systemd
systemd 229-4ubuntu21.1
Execute
SYSTEMD_
A few times, to notice that the output is "jumpy" and the order of the error messages is unstable. Realising that the sorting / application of the sysctls is not performed in a stable order.
Upgraded to
$ dpkg-query -W systemd
systemd 229-4ubuntu21.2
Rerunning the above command again, and again, and again, shows unchanging output on the terminal, meaning the order of all the things that were attempted to be written is now stable.
tags: |
added: verification-done verification-done-xenial removed: verification-needed verification-needed-xenial |
Launchpad Janitor (janitor) wrote : | #4 |
This bug was fixed in the package systemd - 229-4ubuntu21.2
---------------
systemd (229-4ubuntu21.2) xenial; urgency=medium
[ Dimitri John Ledkov ]
* udev: Mark ndb devices as inactive until connected. (LP: #696435)
* networkd: in dhcp, change UseMTU default to true, to accept DHCP provided MTU by default.
(LP: #1717471)
* sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
* networkd: apply promote_
(LP: #1721223)
* shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
* sysctl: do not fail, when cannot apply sysctl changes due to read-only sysfs in containers.
(LP: #1734409)
* networkd,
(LP: #1737570)
[ David Glasser ]
* journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)
-- Dimitri John Ledkov <email address hidden> Wed, 21 Feb 2018 13:46:37 +0000
Changed in systemd (Ubuntu Xenial): | |
status: | Fix Committed → Fix Released |
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.
This is fixed in v232 and up.