This bug was fixed in the package systemd - 232-21ubuntu7
---------------
systemd (232-21ubuntu7) zesty; urgency=medium
* networkd: accept `:' in ifnames in systemd/networkd. (LP: #1714933)
* networkd: add support for ActiveSlave and PrimarySlave netdev options.
(LP: #1709135)
* Cherrypick upstream fix for a race between .mount and .automount units,
which currently may result in automounts hanging. (LP: #1709649)
* systemd.postinst: Fix-up version number check in the previous sru.
The version check in the postinst was too tight, thus the SRU fix failed
validation. (LP: #1710410)
systemd (232-21ubuntu6) zesty; urgency=medium
* link: Fix offload features initialization.
This fixes a regression introduced in v232 which caused TCP
segmentation offloads being disabled by default, resulting in
significant performance issues under certain conditions. (Closes: #864073)
(LP: #1703393)
* loginctl: Fix loginctl ignoring user given session IDs at command-line
(LP: #1682154)
* Disable fallback DNS servers.
This causes resolved to call-home to google, attempt to access network when
none is available, and spams logs. (LP: #1449001)
* initramfs-tools: trigger udevadm add actions with subsystems first.
This updates the initramfs-tools init-top udev script to trigger udevadm
actions with type specified. This mimicks the
systemd-udev-trigger.service. Without type specified only devices are
triggered, but triggering subsystems may also be required and should happen
before triggering the devices. This is the case for example on s390x with
zdev
generated udev rules. (LP: #1713536)
* Enable systemd-resolved by default. (LP: #1710410)
* core: fix systemd failing to serialize tasks correctly on daemon-reload.
(LP: #1702823)
-- Dimitri John Ledkov <x...@ubuntu.com> Wed, 04 Oct 2017 14:22:02
+0100
** Changed in: systemd (Ubuntu Zesty)
Status: Fix Committed => Fix Released
--
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/1702823
Title:
Systemd fails to serialize tasks correctly on daemon-reload
Status in systemd:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Zesty:
Fix Released
Status in systemd source package in Artful:
Fix Released
Status in systemd package in Debian:
Fix Released
Bug description:
[Impact]
A unit with multiple Exec stanzas will loose execution state (which stanzas,
out of multiple, have executed or not) upon systemd daemon-reload during the
execution of these stanzas. This results in lost data/state, and units
potentially failing to start/restart in unpredictable manner
[Testcase]
Setup a race of a unit with multiple exec stanzas (e.g. echo, sleep, echo)
and execute daemon-reload whilst that is in progress. The execution state
should persist across daemon-reload with all exec stanzas completing, in order,
without duplicates.
[Original Bug report]
Hi,
I was initially tracking down a libvirt bug [1], but happened to realize it
is actually a general systemd issue.
From there I got to file, discuss and test [2].
For now I file the bug to be ablte to do my tests correctly, but if it
really fixes the issue I'd like to suggest to fix it in the release -
so better file upfront and do even my test patches right.
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867379
[2]: https://github.com/systemd/systemd/issues/6299.
[Regression Potential]
Minimal, this is a fix for incorrect upstream behaviour which resolves a racy
condition. The code changes are upstream reviewed cherry-pick.
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1702823/+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
