[Touch-packages] [Bug 1457321] Re: lxc-stop does not shut down container
This bug was fixed in the package systemd - 219-7ubuntu6 --- systemd (219-7ubuntu6) vivid; urgency=medium * Fix assertion crash with empty Exec*= paths. (LP: #1454173) * systemd-fsckd autopkgtest: Stop assuming that /etc/default/grub.d/90-autopkgtest.cfg exists. * systemd-fsckd autopkgtest: Add missing plymouth test dependency. * debian/tests/boot-smoke: Allow 10 seconds for systemd jobs to settle down. * Fix tentative state of devices which are not in /dev (mostly in containers), and avoid overzealous cleanup unmounting of mounts from them. (LP: #102) * journal: Gracefully handle failure to bind to audit socket, which is known to fail in namespaces (containers) with current kernels. Also conditionalize systemd-journald-audit.socket on CAP_AUDIT_READ. (LP: #1457054) * Add sigpwr-container-shutdown.service: Power off when receiving SIGPWR in a container. This makes lxc-stop work for systemd containers. (LP: #1457321) -- Martin Pitt martin.p...@ubuntu.com Thu, 21 May 2015 14:47:46 +0200 ** Changed in: systemd (Ubuntu Vivid) 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/1457321 Title: lxc-stop does not shut down container Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Vivid: Fix Released Status in systemd source package in Wily: Fix Released Bug description: lxc-stop sends SIGPWR to a container's pid 1 to notify it that it should shut down. This merely starts sigpwr.target right now, but nothing is hooked into it. That's deliberate for real iron systems as there it's usually UPSes sending that, which should be handled by e. g. nut, not directly systemd. However, for containers I believe that's a safe default. For the record, in upstart we had /etc/init/shutdown.conf . This is wrong, as it breaks UPS responders like nut (and it also halts instead of poweroff). But we should provide this for containers under systemd. https://lists.linuxcontainers.org/pipermail/lxc- users/2015-May/009279.html SRU TEST CASE: -- - Create a vivid LXC container (system or unprivileged) - Try to lxc-stop it. With current vivid it will do nothing/hang, with the proposed version it will shut down as expected. REGRESSION POTENTIAL: - - This new unit is only active in containers (LXC, docker, nspawn, etc.). There a possible regression is that someone is running/testing nut or a similar UPS responder in a container, but that seems like a theoretical scenario only. - There is no change for VMs or real hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457321/+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
[Touch-packages] [Bug 1457321] Re: lxc-stop does not shut down container
I can confirm that vivid containers using the systemd currently in proposed now shut down properly. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1457321 Title: lxc-stop does not shut down container Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Vivid: Fix Committed Status in systemd source package in Wily: Fix Released Bug description: lxc-stop sends SIGPWR to a container's pid 1 to notify it that it should shut down. This merely starts sigpwr.target right now, but nothing is hooked into it. That's deliberate for real iron systems as there it's usually UPSes sending that, which should be handled by e. g. nut, not directly systemd. However, for containers I believe that's a safe default. For the record, in upstart we had /etc/init/shutdown.conf . This is wrong, as it breaks UPS responders like nut (and it also halts instead of poweroff). But we should provide this for containers under systemd. https://lists.linuxcontainers.org/pipermail/lxc- users/2015-May/009279.html SRU TEST CASE: -- - Create a vivid LXC container (system or unprivileged) - Try to lxc-stop it. With current vivid it will do nothing/hang, with the proposed version it will shut down as expected. REGRESSION POTENTIAL: - - This new unit is only active in containers (LXC, docker, nspawn, etc.). There a possible regression is that someone is running/testing nut or a similar UPS responder in a container, but that seems like a theoretical scenario only. - There is no change for VMs or real hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457321/+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
[Touch-packages] [Bug 1457321] Re: lxc-stop does not shut down container
Hello Martin, or anyone else affected, Accepted systemd into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/219-7ubuntu6 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Vivid) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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/1457321 Title: lxc-stop does not shut down container Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Vivid: Fix Committed Status in systemd source package in Wily: Fix Released Bug description: lxc-stop sends SIGPWR to a container's pid 1 to notify it that it should shut down. This merely starts sigpwr.target right now, but nothing is hooked into it. That's deliberate for real iron systems as there it's usually UPSes sending that, which should be handled by e. g. nut, not directly systemd. However, for containers I believe that's a safe default. For the record, in upstart we had /etc/init/shutdown.conf . This is wrong, as it breaks UPS responders like nut (and it also halts instead of poweroff). But we should provide this for containers under systemd. https://lists.linuxcontainers.org/pipermail/lxc- users/2015-May/009279.html SRU TEST CASE: -- - Create a vivid LXC container (system or unprivileged) - Try to lxc-stop it. With current vivid it will do nothing/hang, with the proposed version it will shut down as expected. REGRESSION POTENTIAL: - - This new unit is only active in containers (LXC, docker, nspawn, etc.). There a possible regression is that someone is running/testing nut or a similar UPS responder in a container, but that seems like a theoretical scenario only. - There is no change for VMs or real hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457321/+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
[Touch-packages] [Bug 1457321] Re: lxc-stop does not shut down container
** Description changed: lxc-stop sends SIGPWR to a container's pid 1 to notify it that it should shut down. This merely starts sigpwr.target right now, but nothing is hooked into it. That's deliberate for real iron systems as there it's usually UPSes sending that, which should be handled by e. g. nut, not directly systemd. However, for containers I believe that's a safe default. https://lists.linuxcontainers.org/pipermail/lxc- users/2015-May/009279.html SRU TEST CASE: -- - Create a vivid LXC container (system or unprivileged) - Try to lxc-stop it. With current vivid it will do nothing/hang, with the proposed version it will shut down as expected. + + REGRESSION POTENTIAL: + - + - This new unit is only active in containers (LXC, docker, nspawn, etc.). There a possible regression is that someone is running/testing nut or a similar UPS responder in a container, but that seems like a theoretical scenario only. + - There is no change for VMs or real hardware. ** Description changed: lxc-stop sends SIGPWR to a container's pid 1 to notify it that it should shut down. This merely starts sigpwr.target right now, but nothing is hooked into it. That's deliberate for real iron systems as there it's usually UPSes sending that, which should be handled by e. g. nut, not directly systemd. However, for containers I believe that's a safe default. + + For the record, in upstart we had /etc/init/shutdown.conf . This is + wrong, as it breaks UPS responders like nut (and it also halts instead + of poweroff). But we should provide this for containers under systemd. https://lists.linuxcontainers.org/pipermail/lxc- users/2015-May/009279.html SRU TEST CASE: -- - Create a vivid LXC container (system or unprivileged) - Try to lxc-stop it. With current vivid it will do nothing/hang, with the proposed version it will shut down as expected. REGRESSION POTENTIAL: - - This new unit is only active in containers (LXC, docker, nspawn, etc.). There a possible regression is that someone is running/testing nut or a similar UPS responder in a container, but that seems like a theoretical scenario only. - There is no change for VMs or real hardware. -- 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/1457321 Title: lxc-stop does not shut down container Status in systemd package in Ubuntu: In Progress Status in systemd source package in Vivid: New Status in systemd source package in Wily: In Progress Bug description: lxc-stop sends SIGPWR to a container's pid 1 to notify it that it should shut down. This merely starts sigpwr.target right now, but nothing is hooked into it. That's deliberate for real iron systems as there it's usually UPSes sending that, which should be handled by e. g. nut, not directly systemd. However, for containers I believe that's a safe default. For the record, in upstart we had /etc/init/shutdown.conf . This is wrong, as it breaks UPS responders like nut (and it also halts instead of poweroff). But we should provide this for containers under systemd. https://lists.linuxcontainers.org/pipermail/lxc- users/2015-May/009279.html SRU TEST CASE: -- - Create a vivid LXC container (system or unprivileged) - Try to lxc-stop it. With current vivid it will do nothing/hang, with the proposed version it will shut down as expected. REGRESSION POTENTIAL: - - This new unit is only active in containers (LXC, docker, nspawn, etc.). There a possible regression is that someone is running/testing nut or a similar UPS responder in a container, but that seems like a theoretical scenario only. - There is no change for VMs or real hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457321/+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
[Touch-packages] [Bug 1457321] Re: lxc-stop does not shut down container
Fix for Debian/wily: http://anonscm.debian.org/cgit/pkg- systemd/systemd.git/commit/?h=experimentalid=44c3369f97b Backported for vivid: http://anonscm.debian.org/cgit/pkg- systemd/systemd.git/commit/?h=ubuntu-vividid=7c45c5bc168df ** Changed in: systemd (Ubuntu Wily) Status: In Progress = Fix Committed ** Changed in: systemd (Ubuntu Vivid) Status: New = In Progress -- 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/1457321 Title: lxc-stop does not shut down container Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: In Progress Status in systemd source package in Wily: Fix Committed Bug description: lxc-stop sends SIGPWR to a container's pid 1 to notify it that it should shut down. This merely starts sigpwr.target right now, but nothing is hooked into it. That's deliberate for real iron systems as there it's usually UPSes sending that, which should be handled by e. g. nut, not directly systemd. However, for containers I believe that's a safe default. For the record, in upstart we had /etc/init/shutdown.conf . This is wrong, as it breaks UPS responders like nut (and it also halts instead of poweroff). But we should provide this for containers under systemd. https://lists.linuxcontainers.org/pipermail/lxc- users/2015-May/009279.html SRU TEST CASE: -- - Create a vivid LXC container (system or unprivileged) - Try to lxc-stop it. With current vivid it will do nothing/hang, with the proposed version it will shut down as expected. REGRESSION POTENTIAL: - - This new unit is only active in containers (LXC, docker, nspawn, etc.). There a possible regression is that someone is running/testing nut or a similar UPS responder in a container, but that seems like a theoretical scenario only. - There is no change for VMs or real hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457321/+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
[Touch-packages] [Bug 1457321] Re: lxc-stop does not shut down container
This bug was fixed in the package systemd - 219-10ubuntu1 --- systemd (219-10ubuntu1) wily; urgency=medium * Merge with Debian experimental branch. Remaining Ubuntu changes: - Hack to support system-image read-only /etc, and modify files in /etc/writable/ instead. - Keep our much simpler udev maintainer scripts (all platforms must support udev, no debconf). - initramfs init-top: Drop $ROOTDELAY, we do that in a more sensible way with wait-for-root. Will get applicable to Debian once Debian gets wait-for-root in initramfs-tools. - initramfs init-bottom: If LVM is installed, settle udev, otherwise we get missing LV symlinks. Workaround for LP #1185394. - Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv dependencies to lvm2 which is handled with udev rules in Ubuntu. - Add debian/udev.lvm2.service to avoid running the dummy lvm2 init script. - Provide shutdown fallback for upstart. (LP: #1370329) - debian/extra/ifup@.service: Additionally run for auto class. We don't really support allow-hotplug in Ubuntu at the moment, so we need to deal with auto devices appearing after /etc/init.d/networking start already ran. (LP: #1374521) Also run ifup in the background during boot, to avoid blocking network.target. (LP: #1425376) - ifup@.service: Drop dependency on networking.service (i. e. /etc/init.d/networking), and merely ensure that /run/network exists. This avoids unnecessary dependencies/waiting during boot and dependency cycles if hooks wait for other interfaces to come up (like ifenslave with bonding interfaces). (LP: #1414544) - Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In Ubuntu we currently keep the setting whether the RTC is in local or UTC time in /etc/default/rcS UTC=yes|no, instead of /etc/adjtime. (LP: #1377258) - Put session scopes into all cgroup controllers. This makes unprivileged user LXC containers work under systemd. (LP: #1346734) - systemctl: Don't forward telinit u to upstart. This works around upstart's Restart() always reexec'ing /sbin/init on Restart(), even if that changes to point to systemd during the upgrade. This avoids running systemd during a dist-upgrade. (LP: #1430479) - Drop hwdb-update dependency from udev-trigger.service, which got introduced in v219-stable. This causes udev and plymouth to start too late and isn't really needed in Ubuntu yet as we don't support stateless systems yet and handle hwdb.bin updates through dpkg triggers. This can be dropped again with initramfs-tools 0.117. - Lower Breaks: to plymouth version which has the udev inotify fix in Ubuntu. - Lower libappamor dep to the Ubuntu version where it moved to /lib. - Lower apparmor Breaks: to the Ubuntu version that dropped $remote_fs. - Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681) - Make failure of boot-and-services NSpawn.test_boot non-fatal for now. This currently fails when being triggered by Jenkins, but is totally unreproducible when running this manually on the exact same machine. Upgrade fixes, keep until 16.04 LTS release: - systemd Conflicts/Replaces/Provides systemd-services. - Remove obsolete systemd-logind upstart job. - Clean up obsolete /etc/udev/rules.d/README. systemd (219-10) experimental; urgency=medium * Fix assertion crash with empty Exec*= paths. (LP: #1454173) * Drop Avoid-reload-and-re-start-requests-during-early-boot.patch and Avoid-reloading-services-when-shutting-down.patch: This was fixed more robustly in invoke-rc.d and service now, see #777113. * debian/tests/boot-smoke: Allow 10 seconds for systemd jobs to settle down. * Fix tentative state of devices which are not in /dev (mostly in containers), and avoid overzealous cleanup unmounting of mounts from them. (LP: #102) * debian/extra/udev-helpers/net.agent: Eliminate cat and most grep calls. * Drop Set-default-polling-interval-on-removable-devices-as.patch; it's long obsolete, CD ejection with the hardware button works properly without it. * Re-enable-journal-forwarding-to-syslog.patch: Update patch description, journal.conf.d/ exists now. * journal: Gracefully handle failure to bind to audit socket, which is known to fail in namespaces (containers) with current kernels. Also conditionalize systemd-journald-audit.socket on CAP_AUDIT_READ. (LP: #1457054) * Put back *.agent scripts and use net.agent in Ubuntu. This fixes escaping of unit names, reduces the delta, and will make it easier to get a common solution for integrating ifup.d/ scripts with networkd. * When booting with quiet, run the initramfs' udevd with notice log level. (LP: #1432171) * Add sigpwr-container-shutdown.service: Power off when receiving SIGPWR in a
