Package: systemd Version: 215-17+deb8u3 Tags: patch fixed-upstream User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: jessie-backport
We are currently testing LXC 2.0 beta with unprivileged containers on Ubuntu 16.04/testing and hit a already fixed systemd bug when testing with Debian/Jessie based containers. Currently systemd crashes with an assert in the shutdown path right after unmounting all devices: # lxc stop test02 # ps axf 21568 ? Ss 0:00 [lxc monitor] /var/lib/lxd/containers test02 21584 ? Ss 6:55 \_ /sbin/init 22588 ? Ss 1:10 \_ /lib/systemd/systemd-journald 17093 ? Zs 0:00 \_ [systemctl] <defunct> Attached is a log file with the journalctl output, showing the assert: systemd[1]: Assertion 'sd_id128_randomize(&id) >= 0' failed at ../src/core/dbus.c:688, function bus_on_connection(). Aborting. systemd[1]: Caught <ABRT>, dumped core as pid 15711. systemd[1]: Freezing execution. systemctl[15703]: Failed to execute operation: Connection reset by peer The bug has been reported upstream and fixed in Systemd 219, and we would like to request to include the patch[1] into Jessie. It currently doesn’t affect LXC on a Jessie host, but any platforms on LXC 2.0 with unprivileged containers will run into this issue. In respect of how long Jessie is still going to be around, and the upcoming release of Ubuntu 16.04 this bugfix is important. I’m attaching a link[2] to the initial discussion between Stéphane Graber and Lennart Poettering, and a link[1] to applied patch. Also this[3] seems to be the initial bug report for Ubuntu’s systemd package. Best, Stefan. [1] https://lists.freedesktop.org/archives/systemd-devel/2015-January/027323.html [2] https://github.com/systemd/systemd/commit/874d3404cbf2363604106c8f86683db4082691ea [3] https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1519499
journalctl.log
Description: Binary data