Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/3438
** Bug watch added: github.com/canonical/cloud-init/issues #3438 https://github.com/canonical/cloud-init/issues/3438 ** Changed in: cloud-init Status: Triaged => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1841631 Title: cloud-init.service has no timeout Status in cloud-init: Expired Bug description: cloud-init's systemd service file (cloud-init.service) currently has not timeout; it explicitly sets: TimeoutSec=0 which, while not explicitly documented in systemd-service(5), appears to disable the timeout logic. This may cause the boot process to get stuck, while the system could possibly reach a useful state even if cloud-init failed. We hit this on a headless server: cloud-init got stuck and this prevented systemd to reach the point where systemd-getty-generator would have spawned a getty on the serial line, allowing the server to be accessed remotely. As a result we've got locked out of the server, which had to re rebooted in single-user mode. A cloud-init timeout would have prevented this. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1841631/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
