Bug#979974: cloud-init wait an unnecessary timeout
Package: cloud-init
Version: 20.4-1
Severity: important
Dear Maintainer,
At boot cloud-init waits 120 seconds for an ephemeral disk, but some
VM types doesn't have ephemeral storage at all, so this just blocks
the boot for 120 seconds:
Jan 12 11:23:13 mcroce-buster cloud-init[506]: 2021-01-12 11:23:13,608
- azure.py[WARNING]: ephemeral device '/dev/disk/cloud/azure_resource'
did not appear after 120 seconds.
Please consider mounting the disk upon attach.
Regards,
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-1-cloud-amd64 (SMP w/2 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set
LC_ALL to default locale: No such file or directory
UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages cloud-init depends on:
ii fdisk 2.36.1-4
ii gdisk 1.0.5-1
ii ifupdown 0.8.36
ii locales 2.31-9
ii lsb-base 11.1.0
ii lsb-release 11.1.0
ii net-tools 1.60+git20181103.0eebece-1
ii procps 2:3.3.16-5
ii python3 3.9.1-1
ii python3-configobj 5.0.6-4
ii python3-jinja2 2.11.2-1
ii python3-jsonpatch 1.25-3
ii python3-jsonschema 3.2.0-3
ii python3-oauthlib 3.1.0-2
ii python3-requests 2.25.1+dfsg-2
ii python3-yaml 5.3.1-3+b1
ii util-linux 2.36.1-4
Versions of packages cloud-init recommends:
ii cloud-guest-utils 0.31-2
pn eatmydata <none>
ii sudo 1.9.4p2-2
Versions of packages cloud-init suggests:
pn btrfs-progs <none>
ii e2fsprogs 1.45.6-1
pn xfsprogs <none>
-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_TIME = "it_IT.UTF-8",
LC_MONETARY = "it_IT.UTF-8",
LC_COLLATE = "it_IT.UTF-8",
LC_MEASUREMENT = "it_IT.UTF-8",
LC_NUMERIC = "it_IT.UTF-8",
LANG = "C.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("C.UTF-8").
Report will be sent to Debian Bug Tracking System <submit@bugs.debian.org>
Reply to: