** Summary changed:
- No network in AWS (EC-Classic) after stopping and starging instance
+ No network in AWS (EC-Classic) after stopping and starting instance
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Public bug reported:
I don't know is this cloud-init or netplan or what, but this is not
good.
Background:
# lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
# apt-cache policy cloud-init
cloud-init:
Installed: 18.4-0ubuntu1~18.04.1
Candidate: 18.4-0ubuntu1~18.04.1
V
And little bit more testing. It really seems to be that cloud-init does
not generate the file again if not run clout-init clean before. So it
doesn't generate the file again after stop&start and macaddress differs
and no network, and no network.
Let's test it by editing the file by hand:
$ cat /e
Hi,
Yes probably the regeneration on every boot is better, but without
understanding the internals it was easier for me to manually patch and
remove those from config than trying to figure out how to get it to be
regenerated every boot.
Because wanted to patch manually couple of instances before
