I can confirm that systemd is sending a TERM to (at least) the cloud-init-generator process. However, I'm not yet sure why:
* The cloud-init-generator process typically runs in approximately 30ms, and is sometimes killed. * I've been able to insert an artificial 2s pause in the middle of the script without appearing to impact the frequency of it being killed. * Timing of this specific generator doesn't explain why several other generators are also apparently being killed. The systemd docs (https://manpages.debian.org/unstable/systemd/systemd.generator.7.en.html) indicate that generators are executed synchronously during the boot process and should thus take care to not "delay the entire boot if they are slow". However, there's no mention of a specific runtime requirement. Is the deadline dynamic in some way?
