[10:07] <Porkepix> Hi, I've a little question, did some of you here experiences some issues about AMIs seamingly stuck on boot in some conditions and related to cloud-init? To give some context, we had scripts put as user-data for booting instance and used in a packer report to prepare some AMIs. We wanted to merge those repo and use the same script for both contexts. While it was working well in user-data for
[10:07] <Porkepix> booting instance, packer was stuck with this issue: https://www.packer.io/docs/debugging#issues-installing-ubuntu-packages ; to tackle it, we found out a solution was to use `/usr/bin/cloud-init status --wait`. It worked well for fixing the packer failing, but it also created another issue for instances having this in their user-data: the command is never ending and the user-data log is filling
[10:07] <Porkepix> like that: https://pic.infini.fr/8o6W1LCW/vO0IsI2v.png
[10:09] <Porkepix> So, was it encountered here to have the command never ending and not letting the shell/script take back over?
[17:47] <smoser1> you'd need to share what the command is.  why is the command not exiting ?
[17:47] <smoser1> cloud-init wait wont be "done" until the commands it is running are done. That seems sane, doesn't it?
=== smoser1 is now known as smoser
[17:47] <smoser> Porkepix ?
[18:06] <Porkepix> smoser: Sorry, not at work anymore, but I guess we found out what the issue was, serious miscomprehension of my end that the user-data and scripts it runs are completely part of the cloud-init itself, therefore we created a deadlock were the user-data contained a cloud-init wait, waiting for the end of the user-data itself