| 2016-11-29 11:13:03 |
Christian Ehrhardt |
bug |
|
|
added bug |
| 2016-11-29 15:23:38 |
Christian Ehrhardt |
curtin: status |
New |
Confirmed |
|
| 2016-11-29 15:25:06 |
Christian Ehrhardt |
bug task added |
|
curtin (Ubuntu) |
|
| 2016-11-29 15:25:14 |
Christian Ehrhardt |
curtin (Ubuntu): status |
New |
Confirmed |
|
| 2016-11-29 15:25:21 |
Christian Ehrhardt |
nominated for series |
|
Ubuntu Yakkety |
|
| 2016-11-29 15:25:21 |
Christian Ehrhardt |
bug task added |
|
curtin (Ubuntu Yakkety) |
|
| 2016-11-29 15:25:27 |
Christian Ehrhardt |
curtin (Ubuntu Yakkety): status |
New |
Triaged |
|
| 2016-11-29 15:25:30 |
Christian Ehrhardt |
curtin (Ubuntu Yakkety): importance |
Undecided |
High |
|
| 2016-11-29 16:53:26 |
Christian Ehrhardt |
bug watch added |
|
http://bugs.gnupg.org/gnupg/issue2858 |
|
| 2016-11-29 16:54:17 |
Christian Ehrhardt |
bug task added |
|
gnupg |
|
| 2016-11-29 17:23:48 |
Bug Watch Updater |
gnupg: status |
Unknown |
New |
|
| 2016-11-30 11:01:44 |
Christian Ehrhardt |
branch linked |
|
lp:~paelzer/curtin/curtin-bug-1645680-gpgagent |
|
| 2016-11-30 17:53:49 |
Bug Watch Updater |
gnupg: status |
New |
Incomplete |
|
| 2016-12-01 22:12:21 |
Launchpad Janitor |
branch linked |
|
lp:curtin |
|
| 2016-12-01 22:16:30 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/ubuntu/zesty/curtin/pkg |
|
| 2016-12-02 03:47:41 |
Launchpad Janitor |
curtin (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2017-01-18 16:05:36 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/ubuntu/xenial/curtin/pkg-sru-r437 |
|
| 2017-01-18 17:39:47 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/ubuntu/xenial/curtin/pkg |
|
| 2017-01-18 20:20:39 |
Scott Moser |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-01-18 20:20:39 |
Scott Moser |
bug task added |
|
curtin (Ubuntu Zesty) |
|
| 2017-01-18 20:20:39 |
Scott Moser |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-01-18 20:20:39 |
Scott Moser |
bug task added |
|
curtin (Ubuntu Xenial) |
|
| 2017-01-18 20:20:54 |
Scott Moser |
curtin (Ubuntu Xenial): status |
New |
Fix Released |
|
| 2017-01-18 20:20:59 |
Scott Moser |
curtin (Ubuntu Xenial): status |
Fix Released |
Confirmed |
|
| 2017-01-18 20:21:03 |
Scott Moser |
curtin (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2017-01-18 20:21:10 |
Scott Moser |
curtin (Ubuntu Xenial): status |
Confirmed |
Triaged |
|
| 2017-01-18 20:21:26 |
Scott Moser |
curtin (Ubuntu Zesty): importance |
Undecided |
Medium |
|
| 2017-01-18 21:02:35 |
Scott Moser |
description |
Hi,
while testing I found that when running apt feature related to add-apt-repository like:
apt:
sources:
ignored1:
source: "ppa:paelzer/yourppa"
Or in fact any sort of add-apt-repository (also unrelated to the apt feature itself) like:
late_commands:
01_install_ppa: ['curtin', 'in-target --', 'add-apt-repository --yes ppa:paelzer/bug-1645274-multipath-merge']
Then the installation fails.
Both use the chroot to execute in target, but recent add-apt-repository seems so cause daemons to spawn which then let the umount fail.
Failure is usually around something like:
"umount: /tmp/tmptmucmfm0/target/dev: target is busy"
Here an excerpt from a lsof +fg afterwards.
dirmngr 6771 root 1r CHR LG,0x80000 1,9 0t0 11 /tmp/tmptmucmfm0/target/dev/urandom
dirmngr 6771 root 2w CHR W,LG 1,3 0t0 6 /tmp/tmptmucmfm0/target/dev/null
gpg-agent 6776 root 0r CHR LG 1,3 0t0 6 /tmp/tmptmucmfm0/target/dev/null
gpg-agent 6776 root 1w CHR W,LG 1,3 0t0 6 /tmp/tmptmucmfm0/target/dev/null
gpg-agent 6776 root 2w CHR W,LG 1,3 0t0 6 /tmp/tmptmucmfm0/target/dev/null
One of them could be shut down by:
gpg-connect-agent --verbose KILLAGENT
But not dirmngr, that has to be killed.
Actually killing them seems ok (does not seem to create and later fallout). |
----- Begin SRU Template -----
[Impact]
The mechanism for adding PPAs during was prone to failure when installing
16.10 (yakkety) or newer systems.
A curtin install of yakkety with the following configuration would
fail:
apt:
sources:
ignored1:
source: "ppa:paelzer/yourppa"
[Test Case]
Install a yakkety or zesty system with the above configuration.
[Regression Potential]
[Other Info]
This failure came as a result of change in behavior of gpg. Curtin
(indirectly through add-apt-repository) uses GPG to add PPAs into a
chroot. GPG2 began daemonizing itself, which meant that unmounts of the
filesystem would fail due to open filehandles of the daemonized gpg
process.
There is further discussion both on the bug and in the upstream
merge proposal [1] on other ways to do this. The solution taken was
a killall of processes named 'dirmgr' or 'gpg-agent' that were spawned
after the chroot.
[1] https://code.launchpad.net/~paelzer/curtin/curtin-bug-1645680-gpgagent/+merge/312143
----- End SRU Template -----
Hi,
while testing I found that when running apt feature related to add-apt-repository like:
apt:
sources:
ignored1:
source: "ppa:paelzer/yourppa"
Or in fact any sort of add-apt-repository (also unrelated to the apt feature itself) like:
late_commands:
01_install_ppa: ['curtin', 'in-target --', 'add-apt-repository --yes ppa:paelzer/bug-1645274-multipath-merge']
Then the installation fails.
Both use the chroot to execute in target, but recent add-apt-repository seems so cause daemons to spawn which then let the umount fail.
Failure is usually around something like:
"umount: /tmp/tmptmucmfm0/target/dev: target is busy"
Here an excerpt from a lsof +fg afterwards.
dirmngr 6771 root 1r CHR LG,0x80000 1,9 0t0 11 /tmp/tmptmucmfm0/target/dev/urandom
dirmngr 6771 root 2w CHR W,LG 1,3 0t0 6 /tmp/tmptmucmfm0/target/dev/null
gpg-agent 6776 root 0r CHR LG 1,3 0t0 6 /tmp/tmptmucmfm0/target/dev/null
gpg-agent 6776 root 1w CHR W,LG 1,3 0t0 6 /tmp/tmptmucmfm0/target/dev/null
gpg-agent 6776 root 2w CHR W,LG 1,3 0t0 6 /tmp/tmptmucmfm0/target/dev/null
One of them could be shut down by:
gpg-connect-agent --verbose KILLAGENT
But not dirmngr, that has to be killed.
Actually killing them seems ok (does not seem to create and later fallout). |
|
| 2017-01-18 21:06:53 |
Scott Moser |
description |
----- Begin SRU Template -----
[Impact]
The mechanism for adding PPAs during was prone to failure when installing
16.10 (yakkety) or newer systems.
A curtin install of yakkety with the following configuration would
fail:
apt:
sources:
ignored1:
source: "ppa:paelzer/yourppa"
[Test Case]
Install a yakkety or zesty system with the above configuration.
[Regression Potential]
[Other Info]
This failure came as a result of change in behavior of gpg. Curtin
(indirectly through add-apt-repository) uses GPG to add PPAs into a
chroot. GPG2 began daemonizing itself, which meant that unmounts of the
filesystem would fail due to open filehandles of the daemonized gpg
process.
There is further discussion both on the bug and in the upstream
merge proposal [1] on other ways to do this. The solution taken was
a killall of processes named 'dirmgr' or 'gpg-agent' that were spawned
after the chroot.
[1] https://code.launchpad.net/~paelzer/curtin/curtin-bug-1645680-gpgagent/+merge/312143
----- End SRU Template -----
Hi,
while testing I found that when running apt feature related to add-apt-repository like:
apt:
sources:
ignored1:
source: "ppa:paelzer/yourppa"
Or in fact any sort of add-apt-repository (also unrelated to the apt feature itself) like:
late_commands:
01_install_ppa: ['curtin', 'in-target --', 'add-apt-repository --yes ppa:paelzer/bug-1645274-multipath-merge']
Then the installation fails.
Both use the chroot to execute in target, but recent add-apt-repository seems so cause daemons to spawn which then let the umount fail.
Failure is usually around something like:
"umount: /tmp/tmptmucmfm0/target/dev: target is busy"
Here an excerpt from a lsof +fg afterwards.
dirmngr 6771 root 1r CHR LG,0x80000 1,9 0t0 11 /tmp/tmptmucmfm0/target/dev/urandom
dirmngr 6771 root 2w CHR W,LG 1,3 0t0 6 /tmp/tmptmucmfm0/target/dev/null
gpg-agent 6776 root 0r CHR LG 1,3 0t0 6 /tmp/tmptmucmfm0/target/dev/null
gpg-agent 6776 root 1w CHR W,LG 1,3 0t0 6 /tmp/tmptmucmfm0/target/dev/null
gpg-agent 6776 root 2w CHR W,LG 1,3 0t0 6 /tmp/tmptmucmfm0/target/dev/null
One of them could be shut down by:
gpg-connect-agent --verbose KILLAGENT
But not dirmngr, that has to be killed.
Actually killing them seems ok (does not seem to create and later fallout). |
----- Begin SRU Template -----
[Impact]
The mechanism for adding PPAs during was prone to failure when installing
16.10 (yakkety) or newer systems.
A curtin install of yakkety with the following configuration would
fail:
apt:
sources:
ignored1:
source: "ppa:paelzer/yourppa"
[Test Case]
Install a yakkety or zesty system with the above configuration.
This can be accomplished by running the vmtest YakketyTestAptConfigCMDCMD
with the installed version of curtin.
It has configuration of
apt:
sources:
ignored:
source: "ppa:curtin-dev/test-archive"
curtin-test1.list:
source: "deb $MIRROR $RELEASE-proposed main"
[Regression Potential]
[Other Info]
This failure came as a result of change in behavior of gpg. Curtin
(indirectly through add-apt-repository) uses GPG to add PPAs into a
chroot. GPG2 began daemonizing itself, which meant that unmounts of the
filesystem would fail due to open filehandles of the daemonized gpg
process.
There is further discussion both on the bug and in the upstream
merge proposal [1] on other ways to do this. The solution taken was
a killall of processes named 'dirmgr' or 'gpg-agent' that were spawned
after the chroot.
[1] https://code.launchpad.net/~paelzer/curtin/curtin-bug-1645680-gpgagent/+merge/312143
----- End SRU Template -----
Hi,
while testing I found that when running apt feature related to add-apt-repository like:
apt:
sources:
ignored1:
source: "ppa:paelzer/yourppa"
Or in fact any sort of add-apt-repository (also unrelated to the apt feature itself) like:
late_commands:
01_install_ppa: ['curtin', 'in-target --', 'add-apt-repository --yes ppa:paelzer/bug-1645274-multipath-merge']
Then the installation fails.
Both use the chroot to execute in target, but recent add-apt-repository seems so cause daemons to spawn which then let the umount fail.
Failure is usually around something like:
"umount: /tmp/tmptmucmfm0/target/dev: target is busy"
Here an excerpt from a lsof +fg afterwards.
dirmngr 6771 root 1r CHR LG,0x80000 1,9 0t0 11 /tmp/tmptmucmfm0/target/dev/urandom
dirmngr 6771 root 2w CHR W,LG 1,3 0t0 6 /tmp/tmptmucmfm0/target/dev/null
gpg-agent 6776 root 0r CHR LG 1,3 0t0 6 /tmp/tmptmucmfm0/target/dev/null
gpg-agent 6776 root 1w CHR W,LG 1,3 0t0 6 /tmp/tmptmucmfm0/target/dev/null
gpg-agent 6776 root 2w CHR W,LG 1,3 0t0 6 /tmp/tmptmucmfm0/target/dev/null
One of them could be shut down by:
gpg-connect-agent --verbose KILLAGENT
But not dirmngr, that has to be killed.
Actually killing them seems ok (does not seem to create and later fallout). |
|
| 2017-01-24 10:25:12 |
Łukasz Zemczak |
curtin (Ubuntu Yakkety): status |
Triaged |
Fix Committed |
|
| 2017-01-24 10:25:14 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-01-24 10:25:16 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2017-01-24 10:25:22 |
Łukasz Zemczak |
tags |
|
verification-needed |
|
| 2017-01-31 16:52:00 |
Scott Moser |
curtin: status |
Confirmed |
Fix Committed |
|
| 2017-01-31 16:52:15 |
Scott Moser |
curtin (Ubuntu Xenial): status |
Triaged |
Fix Committed |
|
| 2017-01-31 16:54:33 |
Scott Moser |
tags |
verification-needed |
verification-needed-xenial verification-needed-yakkety |
|
| 2017-01-31 21:37:40 |
Scott Moser |
attachment added |
|
output of vmtests for yakkety run https://bugs.launchpad.net/curtin/+bug/1645680/+attachment/4811532/+files/yakkety-1645680.tar.gz |
|
| 2017-01-31 21:45:20 |
Scott Moser |
tags |
verification-needed-xenial verification-needed-yakkety |
verification-done-yakkety verification-needed-xenial |
|
| 2017-01-31 21:54:35 |
Scott Moser |
attachment added |
|
output of vmtests for xenial run https://bugs.launchpad.net/curtin/+bug/1645680/+attachment/4811552/+files/xenial-1645680.tar.gz |
|
| 2017-01-31 21:55:24 |
Scott Moser |
tags |
verification-done-yakkety verification-needed-xenial |
verification-done-xenial verification-done-yakkety |
|
| 2017-02-01 20:48:41 |
Launchpad Janitor |
curtin (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-02-01 20:48:58 |
Robie Basak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-02-02 16:37:27 |
Launchpad Janitor |
curtin (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2017-02-07 20:24:48 |
Launchpad Janitor |
branch linked |
|
lp:~curtin-dev/curtin/zesty |
|
| 2017-02-17 03:27:31 |
Launchpad Janitor |
branch linked |
|
lp:~curtin-dev/curtin/yakkety |
|
| 2017-05-03 11:14:46 |
Scott Moser |
branch linked |
|
lp:~smoser/maas-images/trunk.use-unshare |
|
| 2017-06-13 22:01:00 |
Launchpad Janitor |
branch linked |
|
lp:~raharper/curtin/merge-unshare-chroot |
|
| 2017-12-15 22:11:07 |
Scott Moser |
curtin: status |
Fix Committed |
Fix Released |
|
