| 2015-05-21 06:07:35 |
Martin Pitt |
bug |
|
|
added bug |
| 2015-05-21 06:07:43 |
Martin Pitt |
nominated for series |
|
Ubuntu Wily |
|
| 2015-05-21 06:07:43 |
Martin Pitt |
bug task added |
|
systemd (Ubuntu Wily) |
|
| 2015-05-21 06:07:43 |
Martin Pitt |
nominated for series |
|
Ubuntu Vivid |
|
| 2015-05-21 06:07:43 |
Martin Pitt |
bug task added |
|
systemd (Ubuntu Vivid) |
|
| 2015-05-21 06:07:53 |
Martin Pitt |
bug |
|
|
added subscriber Stéphane Graber |
| 2015-05-21 06:10:21 |
Martin Pitt |
tags |
|
systemd-boot |
|
| 2015-05-21 06:10:24 |
Martin Pitt |
systemd (Ubuntu Wily): importance |
Undecided |
Medium |
|
| 2015-05-21 06:10:27 |
Martin Pitt |
systemd (Ubuntu Vivid): importance |
Undecided |
Medium |
|
| 2015-05-21 06:13:01 |
Martin Pitt |
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.
https://lists.linuxcontainers.org/pipermail/lxc-users/2015-May/009279.html |
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. |
|
| 2015-05-21 06:13:06 |
Martin Pitt |
systemd (Ubuntu Wily): status |
New |
In Progress |
|
| 2015-05-21 06:13:08 |
Martin Pitt |
systemd (Ubuntu Wily): assignee |
|
Martin Pitt (pitti) |
|
| 2015-05-21 06:18:22 |
Martin Pitt |
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.
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. |
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. |
|
| 2015-05-21 06:21:41 |
Martin Pitt |
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.
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. |
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. |
|
| 2015-05-21 06:34:56 |
Martin Pitt |
systemd (Ubuntu Wily): status |
In Progress |
Fix Committed |
|
| 2015-05-21 06:34:56 |
Martin Pitt |
systemd (Ubuntu Wily): assignee |
Martin Pitt (pitti) |
|
|
| 2015-05-21 06:35:02 |
Martin Pitt |
systemd (Ubuntu Wily): assignee |
|
Martin Pitt (pitti) |
|
| 2015-05-21 06:35:05 |
Martin Pitt |
systemd (Ubuntu Vivid): status |
New |
In Progress |
|
| 2015-05-21 11:13:12 |
Nobuto Murata |
bug |
|
|
added subscriber Nobuto Murata |
| 2015-05-21 12:37:56 |
Launchpad Janitor |
systemd (Ubuntu Wily): status |
Fix Committed |
Fix Released |
|
| 2015-06-02 23:19:32 |
Brian Murray |
systemd (Ubuntu Vivid): status |
In Progress |
Fix Committed |
|
| 2015-06-02 23:19:34 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2015-06-02 23:19:38 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2015-06-02 23:19:44 |
Brian Murray |
tags |
systemd-boot |
systemd-boot verification-needed |
|
| 2015-06-09 17:32:31 |
Stéphane Graber |
tags |
systemd-boot verification-needed |
systemd-boot verification-done |
|
| 2015-06-10 18:21:30 |
Launchpad Janitor |
systemd (Ubuntu Vivid): status |
Fix Committed |
Fix Released |
|
| 2015-06-10 18:21:49 |
Chris J Arges |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
