| 2015-11-17 15:51:20 |
Christopher Townsend |
bug |
|
|
added bug |
| 2015-11-18 18:32:27 |
Stéphane Graber |
nominated for series |
|
Ubuntu Xenial |
|
| 2015-11-18 18:32:27 |
Stéphane Graber |
bug task added |
|
lxc (Ubuntu Xenial) |
|
| 2015-11-18 18:32:27 |
Stéphane Graber |
nominated for series |
|
Ubuntu Trusty |
|
| 2015-11-18 18:32:27 |
Stéphane Graber |
bug task added |
|
lxc (Ubuntu Trusty) |
|
| 2015-11-18 18:32:27 |
Stéphane Graber |
nominated for series |
|
Ubuntu Vivid |
|
| 2015-11-18 18:32:27 |
Stéphane Graber |
bug task added |
|
lxc (Ubuntu Vivid) |
|
| 2015-11-18 18:32:27 |
Stéphane Graber |
nominated for series |
|
Ubuntu Wily |
|
| 2015-11-18 18:32:27 |
Stéphane Graber |
bug task added |
|
lxc (Ubuntu Wily) |
|
| 2015-11-18 18:32:34 |
Stéphane Graber |
lxc (Ubuntu Trusty): status |
New |
Confirmed |
|
| 2015-11-18 18:32:36 |
Stéphane Graber |
lxc (Ubuntu Trusty): status |
Confirmed |
Triaged |
|
| 2015-11-18 18:32:42 |
Stéphane Graber |
bug task deleted |
lxc (Ubuntu Trusty) |
|
|
| 2015-11-18 18:32:47 |
Stéphane Graber |
lxc (Ubuntu Vivid): status |
New |
Triaged |
|
| 2015-11-18 18:32:50 |
Stéphane Graber |
lxc (Ubuntu Wily): status |
New |
Triaged |
|
| 2015-11-18 18:32:53 |
Stéphane Graber |
lxc (Ubuntu Xenial): status |
New |
Triaged |
|
| 2015-11-18 18:32:56 |
Stéphane Graber |
lxc (Ubuntu Vivid): importance |
Undecided |
High |
|
| 2015-11-18 18:32:57 |
Stéphane Graber |
lxc (Ubuntu Wily): importance |
Undecided |
High |
|
| 2015-11-18 18:32:58 |
Stéphane Graber |
lxc (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2015-11-18 18:39:02 |
Stéphane Graber |
lxc (Ubuntu Xenial): status |
Triaged |
Fix Committed |
|
| 2015-11-18 18:56:43 |
Stéphane Graber |
description |
I have a script using the Python3 LXC API that starts up a container. If I use an Upstart job to call the script, the $PATH env var is getting clobbered and the container fails to start. |
== SRU ==
Rationale: LXC 1.1 and higher mangles the process env to be able to re-title itself, breaking the environment for sub-processes in the process
Test case: Spawn a container and check /proc/self/environ
Regression potential: Worst case scenario is we stamp on a different part of the process memory leading to similar but different breakage. It's been tested not to be the case though, change comes from upstream.
== Original bug report ==
I have a script using the Python3 LXC API that starts up a container. If I use an Upstart job to call the script, the $PATH env var is getting clobbered and the container fails to start. |
|
| 2015-11-18 18:58:00 |
Chris J Arges |
lxc (Ubuntu Wily): status |
Triaged |
Fix Committed |
|
| 2015-11-18 18:58:02 |
Chris J Arges |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2015-11-18 18:58:07 |
Chris J Arges |
bug |
|
|
added subscriber SRU Verification |
| 2015-11-18 18:58:14 |
Chris J Arges |
tags |
|
verification-needed |
|
| 2015-11-18 19:01:06 |
Chris J Arges |
lxc (Ubuntu Vivid): status |
Triaged |
Fix Committed |
|
| 2015-11-19 20:52:44 |
Launchpad Janitor |
lxc (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2015-11-23 20:00:50 |
Christopher Townsend |
tags |
verification-needed |
verification-done |
|
| 2015-11-30 17:23:32 |
Launchpad Janitor |
lxc (Ubuntu Vivid): status |
Fix Committed |
Fix Released |
|
| 2015-11-30 17:23:39 |
Launchpad Janitor |
lxc (Ubuntu Wily): status |
Fix Committed |
Fix Released |
|
| 2015-11-30 17:24:19 |
Stéphane Graber |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
