| 2014-01-10 07:32:48 |
Martin Pitt |
bug |
|
|
added bug |
| 2014-01-10 07:33:10 |
Martin Pitt |
nominated for series |
|
Ubuntu Precise |
|
| 2014-01-10 07:33:10 |
Martin Pitt |
bug task added |
|
apport (Ubuntu Precise) |
|
| 2014-01-10 07:33:10 |
Martin Pitt |
nominated for series |
|
Ubuntu Trusty |
|
| 2014-01-10 07:33:10 |
Martin Pitt |
bug task added |
|
apport (Ubuntu Trusty) |
|
| 2014-01-10 07:34:13 |
Launchpad Janitor |
branch linked |
|
lp:apport |
|
| 2014-01-10 07:36:00 |
Martin Pitt |
apport (Ubuntu Trusty): importance |
Undecided |
Medium |
|
| 2014-01-10 07:36:02 |
Martin Pitt |
apport (Ubuntu Precise): importance |
Undecided |
Medium |
|
| 2014-01-10 07:36:04 |
Martin Pitt |
apport (Ubuntu Trusty): assignee |
|
Martin Pitt (pitti) |
|
| 2014-01-10 07:36:05 |
Martin Pitt |
apport (Ubuntu Precise): assignee |
|
Martin Pitt (pitti) |
|
| 2014-01-10 07:41:12 |
Martin Pitt |
description |
As soon as you start/stop a container, or install/remove apport in the container, apport's init.d/upstart script change the global /proc/sys/kernel/core_pattern and thus influence all other containers and the host.
Only the host should set core_pattern, and with https://code.launchpad.net/~stgraber/apport/pidns-support/+merge/200893 crashes in a container are now properly forwarded to the container's apport. |
As soon as you start/stop a container, or install/remove apport in the container, apport's init.d/upstart script change the global /proc/sys/kernel/core_pattern and thus influence all other containers and the host.
Only the host should set core_pattern, and with https://code.launchpad.net/~stgraber/apport/pidns-support/+merge/200893 crashes in a container are now properly forwarded to the container's apport.
SRU TEST CASE (stop):
- Check that apport is currently enabled:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c
- Start a container (that has apport installed):
$ sudo lxc-start-ephemeral -o precise
- Stop the container:
$ sudo poweroff # within the container
- Apport is now disabled globally:
$ cat /proc/sys/kernel/core_pattern
core
With the fixed apport, /proc/sys/kernel/core_pattern should never be touched by the container.
SRU TEST CASE (start):
- Stop apport globally:
$ sudo stop apport
$ cat /proc/sys/kernel/core_pattern
core
- Start a container (that has apport installed):
$ sudo lxc-start-ephemeral -o precise
- Apport is now globally enabled:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c
With the fixed apport, /proc/sys/kernel/core_pattern should never be touched by the container. |
|
| 2014-01-10 07:43:57 |
Martin Pitt |
description |
As soon as you start/stop a container, or install/remove apport in the container, apport's init.d/upstart script change the global /proc/sys/kernel/core_pattern and thus influence all other containers and the host.
Only the host should set core_pattern, and with https://code.launchpad.net/~stgraber/apport/pidns-support/+merge/200893 crashes in a container are now properly forwarded to the container's apport.
SRU TEST CASE (stop):
- Check that apport is currently enabled:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c
- Start a container (that has apport installed):
$ sudo lxc-start-ephemeral -o precise
- Stop the container:
$ sudo poweroff # within the container
- Apport is now disabled globally:
$ cat /proc/sys/kernel/core_pattern
core
With the fixed apport, /proc/sys/kernel/core_pattern should never be touched by the container.
SRU TEST CASE (start):
- Stop apport globally:
$ sudo stop apport
$ cat /proc/sys/kernel/core_pattern
core
- Start a container (that has apport installed):
$ sudo lxc-start-ephemeral -o precise
- Apport is now globally enabled:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c
With the fixed apport, /proc/sys/kernel/core_pattern should never be touched by the container. |
As soon as you start/stop a container, or install/remove apport in the container, apport's init.d/upstart script change the global /proc/sys/kernel/core_pattern and thus influence all other containers and the host.
Only the host should set core_pattern, and with https://code.launchpad.net/~stgraber/apport/pidns-support/+merge/200893 crashes in a container are now properly forwarded to the container's apport.
SRU TEST CASE (stop):
- Check that apport is currently enabled:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c
- Start a container (that has apport installed):
$ sudo lxc-start-ephemeral -o precise
- Stop the container:
$ sudo poweroff # within the container
- Apport is now disabled globally:
$ cat /proc/sys/kernel/core_pattern
core
With the fixed apport, /proc/sys/kernel/core_pattern should never be touched by the container.
SRU TEST CASE (start):
- Stop apport globally:
$ sudo stop apport
$ cat /proc/sys/kernel/core_pattern
core
- Start a container (that has apport installed):
$ sudo lxc-start-ephemeral -o precise
- Apport is now globally enabled:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c
With the fixed apport, /proc/sys/kernel/core_pattern should never be touched by the container.
SRU TEST CASE (regression test):
- Starting/stopping apport manually should still work. After booting, apport should be enabled:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c
$ sudo stop apport
$ cat /proc/sys/kernel/core_pattern
core
$ sudo start apport
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c
REGRESSION POTENTIAL: In releases < trusty, apport would not work in containers at all, as the kernel calls the host's apport; before https://code.launchpad.net/~stgraber/apport/pidns-support/+merge/200893, Apport did not forward crashes that happened in a container to the container's apport, so for precise there is no regresssion potential. |
|
| 2014-01-10 08:08:58 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-core-dev/ubuntu/trusty/apport/ubuntu |
|
| 2014-01-10 08:09:28 |
Martin Pitt |
apport (Ubuntu Trusty): status |
New |
Fix Committed |
|
| 2014-01-10 08:09:28 |
Martin Pitt |
apport (Ubuntu Trusty): assignee |
Martin Pitt (pitti) |
|
|
| 2014-01-10 08:09:36 |
Martin Pitt |
apport (Ubuntu Trusty): assignee |
|
Martin Pitt (pitti) |
|
| 2014-01-10 08:09:45 |
Martin Pitt |
description |
As soon as you start/stop a container, or install/remove apport in the container, apport's init.d/upstart script change the global /proc/sys/kernel/core_pattern and thus influence all other containers and the host.
Only the host should set core_pattern, and with https://code.launchpad.net/~stgraber/apport/pidns-support/+merge/200893 crashes in a container are now properly forwarded to the container's apport.
SRU TEST CASE (stop):
- Check that apport is currently enabled:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c
- Start a container (that has apport installed):
$ sudo lxc-start-ephemeral -o precise
- Stop the container:
$ sudo poweroff # within the container
- Apport is now disabled globally:
$ cat /proc/sys/kernel/core_pattern
core
With the fixed apport, /proc/sys/kernel/core_pattern should never be touched by the container.
SRU TEST CASE (start):
- Stop apport globally:
$ sudo stop apport
$ cat /proc/sys/kernel/core_pattern
core
- Start a container (that has apport installed):
$ sudo lxc-start-ephemeral -o precise
- Apport is now globally enabled:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c
With the fixed apport, /proc/sys/kernel/core_pattern should never be touched by the container.
SRU TEST CASE (regression test):
- Starting/stopping apport manually should still work. After booting, apport should be enabled:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c
$ sudo stop apport
$ cat /proc/sys/kernel/core_pattern
core
$ sudo start apport
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c
REGRESSION POTENTIAL: In releases < trusty, apport would not work in containers at all, as the kernel calls the host's apport; before https://code.launchpad.net/~stgraber/apport/pidns-support/+merge/200893, Apport did not forward crashes that happened in a container to the container's apport, so for precise there is no regresssion potential. |
As soon as you start/stop a container, or install/remove apport in the container, apport's init.d/upstart script change the global /proc/sys/kernel/core_pattern and thus influence all other containers and the host.
Only the host should set core_pattern, and with https://code.launchpad.net/~stgraber/apport/pidns-support/+merge/200893 crashes in a container are now properly forwarded to the container's apport.
FIX: http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/trusty/apport/ubuntu/revision/2274
SRU TEST CASE (stop):
- Check that apport is currently enabled:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c
- Start a container (that has apport installed):
$ sudo lxc-start-ephemeral -o precise
- Stop the container:
$ sudo poweroff # within the container
- Apport is now disabled globally:
$ cat /proc/sys/kernel/core_pattern
core
With the fixed apport, /proc/sys/kernel/core_pattern should never be touched by the container.
SRU TEST CASE (start):
- Stop apport globally:
$ sudo stop apport
$ cat /proc/sys/kernel/core_pattern
core
- Start a container (that has apport installed):
$ sudo lxc-start-ephemeral -o precise
- Apport is now globally enabled:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c
With the fixed apport, /proc/sys/kernel/core_pattern should never be touched by the container.
SRU TEST CASE (regression test):
- Starting/stopping apport manually should still work. After booting, apport should be enabled:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c
$ sudo stop apport
$ cat /proc/sys/kernel/core_pattern
core
$ sudo start apport
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c
REGRESSION POTENTIAL: In releases < trusty, apport would not work in containers at all, as the kernel calls the host's apport; before https://code.launchpad.net/~stgraber/apport/pidns-support/+merge/200893, Apport did not forward crashes that happened in a container to the container's apport, so for precise there is no regresssion potential. |
|
| 2014-01-10 08:09:54 |
Martin Pitt |
bug |
|
|
added subscriber Stéphane Graber |
| 2014-01-10 08:10:05 |
Martin Pitt |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2014-01-10 08:10:10 |
Martin Pitt |
apport (Ubuntu Precise): status |
New |
In Progress |
|
| 2014-01-10 11:08:11 |
Launchpad Janitor |
apport (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2014-01-10 14:51:37 |
Martin Pitt |
apport (Ubuntu Precise): status |
In Progress |
Invalid |
|
