Activity log for bug #1527710

Date Who What changed Old value New value Message
2015-12-18 18:24:09 Scott Moser bug added bug
2015-12-18 18:55:55 Steve Langasek update-notifier (Ubuntu): status New Incomplete
2015-12-18 19:34:44 Christian Ehrhardt  bug added subscriber ChristianEhrhardt
2015-12-18 19:49:54 Christian Ehrhardt  attachment added update-notifier-common_3.165_all.deb https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1527710/+attachment/4537009/+files/update-notifier-common_3.165_all.deb
2015-12-18 19:50:59 Christian Ehrhardt  attachment added xenial_update-notifier.debdiff https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1527710/+attachment/4537011/+files/xenial_update-notifier.debdiff
2015-12-18 20:21:44 Ubuntu Foundations Team Bug Bot tags amd64 apport-bug ec2-images xenial amd64 apport-bug ec2-images patch xenial
2015-12-18 20:21:51 Ubuntu Foundations Team Bug Bot bug added subscriber Ubuntu Sponsors Team
2015-12-19 04:08:19 Mathew Hodson update-notifier (Ubuntu): importance Undecided Medium
2015-12-22 15:25:20 Michael Terry removed subscriber Ubuntu Sponsors Team
2016-01-13 21:30:30 Scott Moser update-notifier (Ubuntu): status Incomplete Confirmed
2016-01-27 22:04:57 Brian Murray bug added subscriber Brian Murray
2016-01-27 23:01:46 Launchpad Janitor update-notifier (Ubuntu): status Confirmed Fix Released
2016-01-28 14:38:36 Scott Moser description I have a work flow (curtin installation) that does something to the affect of: mount $DEVICE /target mount --bind /dev /target/dev chroot /target apt-get update umount /target/dev umount /target/ With xenial, I started having failures on the umount of /target/dev because of open file handles. An lsof showed me that /usr/lib/update-notifier/update-motd-updates-available had open file handles on /dev/null and apt-check had handles on /dev/urandom. I admit that part of this is my fault, because we do a selective apt-get update (only pulling deb sources, not deb-src). As a result, when /usr/lib/update-notifier/update-motd-updates-available there was possibly more work to be done then would normally have to be done... not sure on that. For the record, what we do is in http://bazaar.launchpad.net/~curtin-dev/curtin/trunk/view/head:/curtin/util.py#L486 (apt_update method). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: update-notifier-common 3.164 ProcVersionSignature: User Name 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 Date: Fri Dec 18 18:02:41 2015 Ec2AMI: ami-0000072f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: None Ec2Ramdisk: None PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-notifier UpgradeStatus: No upgrade log present (probably fresh install) I have a work flow (curtin installation) that does something to the affect of:  mount $DEVICE /target  mount --bind /dev /target/dev  chroot /target apt-get update  umount /target/dev  umount /target/ With xenial, I started having failures on the umount of /target/dev because of open file handles. An lsof showed me that /usr/lib/update-notifier/update-motd-updates-available had open file handles on /dev/null and apt-check had handles on /dev/urandom. I admit that part of this is my fault, because we do a selective apt-get update (only pulling deb sources, not deb-src). As a result, when /usr/lib/update-notifier/update-motd-updates-available there was possibly more work to be done then would normally have to be done... not sure on that. For the record, what we do is in http://bazaar.launchpad.net/~curtin-dev/curtin/trunk/view/head:/curtin/util.py#L486 (apt_update method). Related bugs: * bug 524674: apt-check hangs, preventing login via SSH * bug 1527710: apt-get update triggers asynchronous task * bug 1533243: preseeded installation fails on critical question: partman/unmount_active DISKS /dev/vda ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: update-notifier-common 3.164 ProcVersionSignature: User Name 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 Date: Fri Dec 18 18:02:41 2015 Ec2AMI: ami-0000072f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: None Ec2Ramdisk: None PackageArchitecture: all ProcEnviron:  TERM=xterm-256color  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=en_US.UTF-8  SHELL=/bin/bash SourcePackage: update-notifier UpgradeStatus: No upgrade log present (probably fresh install)
2016-01-28 16:26:04 Scott Moser bug watch added http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809441