Cloud provider AWS. Debian Stretch images (9.5). Cloud-init v0.7.9-2 Built AMI in an ASG, rarely will fail to run the user-data script. Succeeds about 9 in 10 times, fails the other 1.
cloud-init-output.log ending looks like this when it fails: Generating public/private ed25519 key pair. Your identification has been saved in /etc/ssh/ssh_host_ed25519_key. Your public key has been saved in /etc/ssh/ssh_host_ed25519_key.pub. The key fingerprint is: SHA256:y1DX7UpYgc+hmjyuHgq58H0oHk+ivJctTTCShX2Z+rw root@ip-172-20-137-71 The key's randomart image is: +--[ED25519 256]--+ | o o .. | | . o + ...o | | o o . .+o.. | | o + . ..oo. | | . = ..So. . . | | . + o=. . . | |. = *.o.o. . | |.+.%.E... | |.+*.=oo. | +----[SHA256]-----+ Cloud-init v. 0.7.9 running 'modules:config' at Mon, 03 Dec 2018 23:37:42 +0000. Up 9.99 seconds. 2018-12-03 23:37:42,924 - ug_util.py[WARNING]: Format for 'users' key must be a comma separated string or a dictionary or a list and not NoneType Generating locales (this might take a while)... en_US.UTF-8... done Generation complete. The /var/lib/cloud/boot-finished file does NOT get created when it fails. If I'm parsing /var/lib/cloud/instance/sem/* correctly, it tries the config_byobu module (?) before it goes off the rails. cloud-init does download the correct user-data script to /var/lib/cloud/instance/user-data.txt . The first two lines of the user-data script are: #!/bin/bash echo "I am here" | /usr/bin/tee -a /tmp/uds-logging that output doesn't show up in cloud-init-output, nor in /tmp/uds-logging I have captured the cloud-init.log from a failure run. I'm happy to share it if requested. Interesting difference between a success: main.py[DEBUG]: Ran 17 modules with 0 failures and a failure: main.py[DEBUG]: Ran 12 modules with 0 failures Thank you for any assistance, and please let me know how I can help. Jason
