dgarvey: Thanks for reporting back. I'm glad you figured it out. It sounds like this has been resolved. Since I don't think this was an issue with cloud-init, I'm marking it as "Invalid". Please reopen this bug with more details if you believe that further action is required for cloud-init.
Regards, Brett Holman ** Changed in: cloud-init Status: Incomplete => Invalid -- 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/1971105 Title: cloud-init not initing... Status in cloud-init: Invalid Bug description: I am seeing systemd reset here. [root@sdo-img-rhel79-test-apr30 cloud-init_debug]# dmesg | grep -i term [ 133.522528] systemd-journald[103]: Received SIGTERM from PID 1 (systemd). [root@sdo-img-rhel79-test-apr30 cloud-init_debug]# dmesg > dmesg.txt [root@sdo-img-rhel79-test-apr30 cloud-init_debug]# To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1971105/+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