The same problem also happens in EC2-VPC mode if the network interface changes.
This happens if you create a custom AMI, e.g. using Packer, from the official
Ubuntu 18.04 LTS AMI. The first start by packer writes the MAC address into
/etc/netplan/50-cloud-init.yaml which gets part of the custom AMI. If you then
try to launch an instance from that AMI it gets a new network interface with a
new MAC address and the instance will not have any internet connection.
I tries to call "cloud-init clean" at the end of the packer build but that
didn't have any positive effect.
It seems the current approach is kind of broken in general.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802073
Title:
No network in AWS (EC-Classic) after stopping and starting instance
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1802073/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs