I’ve got an Ubuntu 18 droplet that hangs indefinitely at some point during the boot process on cloudinit. When I reboot it, I have to connect to the console and press ctrl-c to allow a normal boot to continue.

systemd-analyze blame confirms that cloud-init-local.service is active when this hang occurs:

9h 58min 6.762s cloud-init-local.service

However, /var/log/cloud-init.log makes it look as if the system was doing something else before cloudinit was started (note the uptime):

2019-03-02 17:10:48,269 - util.py[DEBUG]: Cloud-init v. 18.4-0ubuntu1~18.04.1 running 'init-local' at Sat, 02 Mar 2019 17:10:48 +0000. Up 35890.58 seconds.

This is also confirmed by the journal:

Mar 02 02:12:42 isengard systemd-udevd[728]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 02 02:12:42 isengard systemd[1]: Found device Virtio network device.
Mar 02 02:12:42 isengard systemd[1]: Found device Virtio network device.
Mar 02 12:10:48 isengard kernel: random: nonblocking pool is initialized
Mar 02 12:10:48 isengard cloud-init[696]: Cloud-init v. 18.4-0ubuntu1~18.04.1 running 'init-local' at Sat, 02 Mar 2019 17:10:48 +0000. Up 35890.58 seconds.
Mar 02 12:10:48 isengard systemd[1]: Started Initial cloud-init job (pre-networking).

Is there a way to increase the verbosity of both the boot process and cloudinit so I can find where this hang is located?