Excellent news! Thanks for following up with Kali upstream. I'm closing this issue as invalid for cloud-init. If you find out after the Kali changes there are still issues, either re-open this bug or file a new one if the issue/behavior is different.
Thanks! ** 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/1869430 Title: cloud-init persists in running state on Kali in AWS Status in cloud-init: Invalid Bug description: Hello, We're trying to customize published Kali AMIs using packer & cloud- init. The entire process works with Ubuntu, CentOS, and Amazon Linux 2 targets, but seemingly breaks with Kali. We've tried it with both the 2020.01 and 2019.03. We're also experiencing a long timeout for ec2 data source: root@kali:~# cloud-init status --long status: running time: Fri, 27 Mar 2020 20:06:54 +0000 detail: DataSourceEc2Local root@kali:~# cloud-init analyze blame -- Boot Record 01 -- 51.20500s (init-local/search-Ec2Local) 00.91700s (init-network/config-users-groups) 00.67200s (init-network/config-growpart) 00.27400s (init-network/config-resizefs) 00.24800s (init-network/config-ssh) 00.00600s (init-network/consume-user-data) 00.00300s (init-network/check-cache) Attached is the log tarball produced by cloud-init. We'd appreciate any hints as to what may be happening. It's worth noting that these targets are starting in a VPC without direct connection to the outside world, but there's a squid proxy available for web traffic. We have relevant parts set up to use that proxy. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1869430/+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