ds-identify - stuck in uninterruptible sleep state
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Invalid
|
Undecided
|
Unassigned | ||
util-linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
We got recurring issues with the cloud-init/
The processes cannot be killed, so the only solution is to reboot the affected server.
root 3839 0.0 0.0 4760 1840 ? S Dec05 0:00 /bin/sh /usr/lib/
root 3844 0.0 0.0 11212 2836 ? D Dec05 0:00 \_ blkid -c /dev/null -o export
root 6943 0.0 0.0 4760 1880 ? S Dec05 0:00 /bin/sh /usr/lib/
root 6948 0.0 0.0 11212 2844 ? D Dec05 0:00 \_ blkid -c /dev/null -o export
root 6111 0.0 0.0 4760 1916 ? S Dec12 0:00 /bin/sh /usr/lib/
root 6149 0.0 0.0 11212 2940 ? D Dec12 0:00 \_ blkid -c /dev/null -o export
root 8765 0.0 0.3 926528 24968 ? Ssl Dec12 0:12 /usr/lib/
root 9179 0.0 0.0 4760 1892 ? S Dec12 0:00 /bin/sh /usr/lib/
root 9185 0.0 0.0 11980 3552 ? D Dec12 0:00 \_ blkid -c /dev/null -o export
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
tags: | added: rls-bb-incoming |
Hi Nicklas,
Thanks for the bug report, this is a bit of a strange one! `blkid` hanging suggests a deeper issue with your VM/hypervisor than just a cloud-init issue, but let's gather the info we need to work that out. Could you run `cloud-init collect-logs` on an affected machine and attach the tarball it creates to this bug, please?
What happens if you run `sudo blkid -c /dev/null -o export` manually on the instance?
(Once you've attached this requested info, please move the bug status back to New.)
Thanks!
Dan