Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3520
** Bug watch added: github.com/canonical/cloud-init/issues #3520
https://github.com/canonical/cloud-init/issues/3520
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Here is the output of `ls -latr /proc//fd`
root 3377 0.0 0.0 11980 3352 ?DJan24 0:00 blkid -c
/dev/null -o export
root 6293 0.0 0.0 11980 3316 ?DJan24 0:00 blkid -c
/dev/null -o export
root 10422 0.0 0.0 11980 3556 ?DJan26
Affected process
```
root 1166 0.0 0.0 72292 5812 ?Ss2019 0:00 /usr/sbin/sshd
-D
```
Output of `ls -latr /proc/1166/fd`
total 0
dr-xr-xr-x 9 root root 0 Jan 14 12:00 ..
dr-x-- 2 root root 0 Jan 14 12:31 .
lrwx-- 1 root root 64 Jan 14 12:31 4 -> 'socket:[24485]'
Never mind my last message...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1856560
Title:
ds-identify - stuck in uninterruptible sleep state
Status in cloud-init:
Moved back to New, because this is happening in normal cloud-init
operation.
** Changed in: util-linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
> If someone manually installs Ubuntu Desktop / Server using an installer,
> one should not be installing or using cloud-init as clearly, it will never
> complete without a correct metadata source present. And when it fails to
> complete, it re-attempts to reprovision the machine on every boot.
cloud-init is used to perform first time configuration of cloud-images
using a cloud metadata source. I.e. a generic image is launched by
openstack and provisions per-user keys / packages / etc.
If someone manually installs Ubuntu Desktop / Server using an installer,
one should not be installing
Hey,
We have restarted the affect nodes/servers. I will retrieve the output
of `ls -latr /proc//fd` once it starts happening again. Often takes
a few days.
I haven't setup our Ubuntu environments. Our IT/devops team (with no
experience of linux) has installed the Ubuntu-nodes on our VMware
[0.00] Command line: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity
[0.00] DMI: VMware, Inc. VMware Virtual Platform/440BX Desktop
Reference Platform, BIOS 6.00 09/21/2015
[0.00] Hypervisor detected: VMware
Could you please
ls -latr /proc//fd
would be nice too, to see what it has open/holding/reading.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1856560
Title:
ds-identify - stuck in
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1856560
Title:
ds-identify - stuck in uninterruptible sleep state
Status in cloud-init:
Hi Nicklas,
Thanks for the extra info! This sounds like an issue with blkid (and/or
your system), rather than a cloud-init bug. I've added a util-linux bug
task (which is the package that ships blkid), and I'm going to mark the
cloud-init bug task Invalid as I don't believe that there's
12 matches
Mail list logo
