In my opinion this is serious bug. I created an AWS AMI using packer and
one of the installed packages (salt-minion) pulled in ifupdown. This
then broke network connectivity of instances started from the custom
AMI. I took me five hours to find out what the problem was.
--
You received this bug
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Status: Expired => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832381
[Expired for cloud-init (Ubuntu) because there has been no activity for
60 days.]
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Do you happen to have a cloud-init collect-logs output ? I suspect it's
easy enough to recreate bug if you've already got logs available, please
attach.
** Summary changed:
- vm fails to boot due to conflicting network configuration when cloudinit
switches from netplan to eni
+ vm fails to
