| 2017-06-16 03:30:16 |
Thiago Alves Silva |
bug |
|
|
added bug |
| 2017-06-16 04:00:06 |
Joseph Salisbury |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2017-06-16 11:45:51 |
Thiago Alves Silva |
tags |
|
apport-collected ec2-images xenial |
|
| 2017-06-16 11:45:52 |
Thiago Alves Silva |
description |
(please refer to https://github.com/moby/moby/issues/31007#issuecomment-308877825 for context)
Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)
Steps to reproduce:
- Install latest Docker
- Run 300 containers with health check (for i in {1..300}; do docker run -d -it --restart=always --name poc_$i talves/health_poc; done)
- Send termination signal to the containers (docker kill -s TERM $(docker ps -q)
- A few processes are going to be stuck in "uninterruptible sleep" ("D" state). The only know way to recover from this is host reboot
Expected behavior:
- All containers should be terminated without any dangling process
Actual behavior:
- Some processes are left in "D" state. In our production environment this leads over time to performance degradation and maintenance issues due to containers that cannot be stopped / removed.
A fix is provided on kernel 4.12 - it would be nice if it could be backported and included in the next Ubuntu release within the supported kernel.
Thanks in advance |
(please refer to https://github.com/moby/moby/issues/31007#issuecomment-308877825 for context)
Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)
Steps to reproduce:
- Install latest Docker
- Run 300 containers with health check (for i in {1..300}; do docker run -d -it --restart=always --name poc_$i talves/health_poc; done)
- Send termination signal to the containers (docker kill -s TERM $(docker ps -q)
- A few processes are going to be stuck in "uninterruptible sleep" ("D" state). The only know way to recover from this is host reboot
Expected behavior:
- All containers should be terminated without any dangling process
Actual behavior:
- Some processes are left in "D" state. In our production environment this leads over time to performance degradation and maintenance issues due to containers that cannot be stopped / removed.
A fix is provided on kernel 4.12 - it would be nice if it could be backported and included in the next Ubuntu release within the supported kernel.
Thanks in advance
---
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 May 29 16:54 seq
crw-rw---- 1 root audio 116, 33 May 29 16:54 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse:
Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Cannot stat file /proc/11652/fd/4: Stale file handle
Cannot stat file /proc/11652/fd/5: Stale file handle
Cannot stat file /proc/11652/fd/6: Stale file handle
Cannot stat file /proc/11652/fd/7: Stale file handle
Cannot stat file /proc/11652/fd/11: Stale file handle
DistroRelease: Ubuntu 16.04
Ec2AMI: ami-45b69e52
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1c
Ec2InstanceType: t2.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Xen HVM domU
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic root=UUID=9b05a884-ac72-4bd2-8660-3bfa5cb22246 ro net.ifnames=0 biosdevname=0 cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
RelatedPackageVersions:
linux-restricted-modules-4.4.0-78-generic N/A
linux-backports-modules-4.4.0-78-generic N/A
linux-firmware 1.157.10
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial ec2-images
Uname: Linux 4.4.0-78-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 02/16/2017
dmi.bios.vendor: Xen
dmi.bios.version: 4.2.amazon
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd02/16/2017:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
dmi.product.name: HVM domU
dmi.product.version: 4.2.amazon
dmi.sys.vendor: Xen |
|
| 2017-06-16 11:45:52 |
Thiago Alves Silva |
attachment added |
|
CRDA.txt https://bugs.launchpad.net/bugs/1698264/+attachment/4897090/+files/CRDA.txt |
|
| 2017-06-16 11:45:54 |
Thiago Alves Silva |
attachment added |
|
CurrentDmesg.txt https://bugs.launchpad.net/bugs/1698264/+attachment/4897091/+files/CurrentDmesg.txt |
|
| 2017-06-16 11:45:55 |
Thiago Alves Silva |
attachment added |
|
JournalErrors.txt https://bugs.launchpad.net/bugs/1698264/+attachment/4897092/+files/JournalErrors.txt |
|
| 2017-06-16 11:45:56 |
Thiago Alves Silva |
attachment added |
|
Lspci.txt https://bugs.launchpad.net/bugs/1698264/+attachment/4897093/+files/Lspci.txt |
|
| 2017-06-16 11:45:57 |
Thiago Alves Silva |
attachment added |
|
ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1698264/+attachment/4897094/+files/ProcCpuinfo.txt |
|
| 2017-06-16 11:45:58 |
Thiago Alves Silva |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1698264/+attachment/4897095/+files/ProcCpuinfoMinimal.txt |
|
| 2017-06-16 11:46:00 |
Thiago Alves Silva |
attachment added |
|
ProcInterrupts.txt https://bugs.launchpad.net/bugs/1698264/+attachment/4897096/+files/ProcInterrupts.txt |
|
| 2017-06-16 11:46:01 |
Thiago Alves Silva |
attachment added |
|
ProcModules.txt https://bugs.launchpad.net/bugs/1698264/+attachment/4897097/+files/ProcModules.txt |
|
| 2017-06-16 11:46:02 |
Thiago Alves Silva |
attachment added |
|
UdevDb.txt https://bugs.launchpad.net/bugs/1698264/+attachment/4897098/+files/UdevDb.txt |
|
| 2017-06-16 11:46:04 |
Thiago Alves Silva |
attachment added |
|
WifiSyslog.txt https://bugs.launchpad.net/bugs/1698264/+attachment/4897099/+files/WifiSyslog.txt |
|
| 2017-06-16 11:47:40 |
Thiago Alves Silva |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2017-06-16 12:37:55 |
Seth Forshee |
linux (Ubuntu): importance |
Undecided |
Medium |
|
| 2017-06-16 12:37:58 |
Seth Forshee |
linux (Ubuntu): assignee |
|
Seth Forshee (sforshee) |
|
| 2017-06-16 16:08:29 |
Seth Forshee |
linux (Ubuntu): status |
Confirmed |
Incomplete |
|
| 2017-06-19 12:26:28 |
Seth Forshee |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-06-19 12:26:28 |
Seth Forshee |
bug task added |
|
linux (Ubuntu Zesty) |
|
| 2017-06-19 12:26:28 |
Seth Forshee |
nominated for series |
|
Ubuntu Yakkety |
|
| 2017-06-19 12:26:28 |
Seth Forshee |
bug task added |
|
linux (Ubuntu Yakkety) |
|
| 2017-06-19 12:26:28 |
Seth Forshee |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-06-19 12:26:28 |
Seth Forshee |
bug task added |
|
linux (Ubuntu Xenial) |
|
| 2017-06-19 12:26:42 |
Seth Forshee |
linux (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2017-06-19 12:26:42 |
Seth Forshee |
linux (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2017-06-19 12:26:42 |
Seth Forshee |
linux (Ubuntu Xenial): assignee |
|
Seth Forshee (sforshee) |
|
| 2017-06-19 12:26:56 |
Seth Forshee |
linux (Ubuntu Yakkety): importance |
Undecided |
Medium |
|
| 2017-06-19 12:26:56 |
Seth Forshee |
linux (Ubuntu Yakkety): status |
New |
In Progress |
|
| 2017-06-19 12:26:56 |
Seth Forshee |
linux (Ubuntu Yakkety): assignee |
|
Seth Forshee (sforshee) |
|
| 2017-06-19 12:27:08 |
Seth Forshee |
linux (Ubuntu Zesty): importance |
Undecided |
Medium |
|
| 2017-06-19 12:27:08 |
Seth Forshee |
linux (Ubuntu Zesty): status |
New |
In Progress |
|
| 2017-06-19 12:27:08 |
Seth Forshee |
linux (Ubuntu Zesty): assignee |
|
Seth Forshee (sforshee) |
|
| 2017-06-19 12:27:15 |
Seth Forshee |
linux (Ubuntu): status |
Incomplete |
Fix Committed |
|
| 2017-06-19 12:50:40 |
Seth Forshee |
description |
(please refer to https://github.com/moby/moby/issues/31007#issuecomment-308877825 for context)
Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)
Steps to reproduce:
- Install latest Docker
- Run 300 containers with health check (for i in {1..300}; do docker run -d -it --restart=always --name poc_$i talves/health_poc; done)
- Send termination signal to the containers (docker kill -s TERM $(docker ps -q)
- A few processes are going to be stuck in "uninterruptible sleep" ("D" state). The only know way to recover from this is host reboot
Expected behavior:
- All containers should be terminated without any dangling process
Actual behavior:
- Some processes are left in "D" state. In our production environment this leads over time to performance degradation and maintenance issues due to containers that cannot be stopped / removed.
A fix is provided on kernel 4.12 - it would be nice if it could be backported and included in the next Ubuntu release within the supported kernel.
Thanks in advance
---
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 May 29 16:54 seq
crw-rw---- 1 root audio 116, 33 May 29 16:54 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse:
Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Cannot stat file /proc/11652/fd/4: Stale file handle
Cannot stat file /proc/11652/fd/5: Stale file handle
Cannot stat file /proc/11652/fd/6: Stale file handle
Cannot stat file /proc/11652/fd/7: Stale file handle
Cannot stat file /proc/11652/fd/11: Stale file handle
DistroRelease: Ubuntu 16.04
Ec2AMI: ami-45b69e52
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1c
Ec2InstanceType: t2.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Xen HVM domU
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic root=UUID=9b05a884-ac72-4bd2-8660-3bfa5cb22246 ro net.ifnames=0 biosdevname=0 cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
RelatedPackageVersions:
linux-restricted-modules-4.4.0-78-generic N/A
linux-backports-modules-4.4.0-78-generic N/A
linux-firmware 1.157.10
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial ec2-images
Uname: Linux 4.4.0-78-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 02/16/2017
dmi.bios.vendor: Xen
dmi.bios.version: 4.2.amazon
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd02/16/2017:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
dmi.product.name: HVM domU
dmi.product.version: 4.2.amazon
dmi.sys.vendor: Xen |
SRU Justification
Impact: In some cases some docker processes can be stuck in the D state after a container has terminated. They will remain in this state until reboot.
Fix: Cherry pick upstream commit b9a985db98961ae1ba0be169f19df1c567e4ffe0, which has already been included as a stable commit in maintained upstream stable kernels.
Test case: See below.
Regression potential: Low, this is a simple change and as stated above the patch has already been shipped out in upstream stable kernels.
---
(please refer to https://github.com/moby/moby/issues/31007#issuecomment-308877825 for context)
Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)
Steps to reproduce:
- Install latest Docker
- Run 300 containers with health check (for i in {1..300}; do docker run -d -it --restart=always --name poc_$i talves/health_poc; done)
- Send termination signal to the containers (docker kill -s TERM $(docker ps -q)
- A few processes are going to be stuck in "uninterruptible sleep" ("D" state). The only know way to recover from this is host reboot
Expected behavior:
- All containers should be terminated without any dangling process
Actual behavior:
- Some processes are left in "D" state. In our production environment this leads over time to performance degradation and maintenance issues due to containers that cannot be stopped / removed.
A fix is provided on kernel 4.12 - it would be nice if it could be backported and included in the next Ubuntu release within the supported kernel.
Thanks in advance
---
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 May 29 16:54 seq
crw-rw---- 1 root audio 116, 33 May 29 16:54 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse:
Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Cannot stat file /proc/11652/fd/4: Stale file handle
Cannot stat file /proc/11652/fd/5: Stale file handle
Cannot stat file /proc/11652/fd/6: Stale file handle
Cannot stat file /proc/11652/fd/7: Stale file handle
Cannot stat file /proc/11652/fd/11: Stale file handle
DistroRelease: Ubuntu 16.04
Ec2AMI: ami-45b69e52
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1c
Ec2InstanceType: t2.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Xen HVM domU
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic root=UUID=9b05a884-ac72-4bd2-8660-3bfa5cb22246 ro net.ifnames=0 biosdevname=0 cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
RelatedPackageVersions:
linux-restricted-modules-4.4.0-78-generic N/A
linux-backports-modules-4.4.0-78-generic N/A
linux-firmware 1.157.10
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial ec2-images
Uname: Linux 4.4.0-78-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 02/16/2017
dmi.bios.vendor: Xen
dmi.bios.version: 4.2.amazon
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd02/16/2017:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
dmi.product.name: HVM domU
dmi.product.version: 4.2.amazon
dmi.sys.vendor: Xen |
|
| 2017-06-21 11:27:19 |
Stefan Bader |
linux (Ubuntu Yakkety): status |
In Progress |
Fix Committed |
|
| 2017-06-21 11:27:22 |
Stefan Bader |
linux (Ubuntu Zesty): status |
In Progress |
Fix Committed |
|
| 2017-07-10 08:22:29 |
Kleber Sacilotto de Souza |
tags |
apport-collected ec2-images xenial |
apport-collected ec2-images verification-needed-yakkety xenial |
|
| 2017-07-10 08:23:41 |
Kleber Sacilotto de Souza |
tags |
apport-collected ec2-images verification-needed-yakkety xenial |
apport-collected ec2-images verification-needed-yakkety verification-needed-zesty xenial |
|
| 2017-07-13 14:06:09 |
Kleber Sacilotto de Souza |
linux (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-07-14 09:00:34 |
Kleber Sacilotto de Souza |
tags |
apport-collected ec2-images verification-needed-yakkety verification-needed-zesty xenial |
apport-collected ec2-images verification-done-yakkety verification-done-zesty xenial |
|
| 2017-07-17 11:38:54 |
Launchpad Janitor |
linux (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2017-07-17 11:38:54 |
Launchpad Janitor |
cve linked |
|
2014-9900 |
|
| 2017-07-17 11:38:54 |
Launchpad Janitor |
cve linked |
|
2016-9755 |
|
| 2017-07-17 11:38:54 |
Launchpad Janitor |
cve linked |
|
2017-1000380 |
|
| 2017-07-17 11:38:54 |
Launchpad Janitor |
cve linked |
|
2017-5551 |
|
| 2017-07-17 11:38:54 |
Launchpad Janitor |
cve linked |
|
2017-5576 |
|
| 2017-07-17 11:38:54 |
Launchpad Janitor |
cve linked |
|
2017-7346 |
|
| 2017-07-17 11:38:54 |
Launchpad Janitor |
cve linked |
|
2017-7895 |
|
| 2017-07-17 11:38:54 |
Launchpad Janitor |
cve linked |
|
2017-8924 |
|
| 2017-07-17 11:38:54 |
Launchpad Janitor |
cve linked |
|
2017-8925 |
|
| 2017-07-17 11:38:54 |
Launchpad Janitor |
cve linked |
|
2017-9074 |
|
| 2017-07-17 11:38:54 |
Launchpad Janitor |
cve linked |
|
2017-9150 |
|
| 2017-07-17 11:38:54 |
Launchpad Janitor |
cve linked |
|
2017-9605 |
|
| 2017-07-17 11:57:59 |
Launchpad Janitor |
linux (Ubuntu Zesty): status |
Fix Committed |
Fix Released |
|
| 2019-10-03 08:14:38 |
Po-Hsu Lin |
linux (Ubuntu): status |
Fix Committed |
Fix Released |
|
