We have a pipeline for building Ubuntu 16.04 images using packer - works great - but when we tried to switch to 18.04 or 20.04 - the resulting AMIs are having trouble getting network when they boot - resulting in instances stuck in “waiting for network” limbo - there must have been something changed between 16.04 and 18.04 - but I am not sure what. Anyone run into this?
Startup console is full of messages like:
A start job is running for Wait for…k to be Configured (2s / no limit)
I have removed most of our provisioning steps, and we are still seeing this