Thank you very much Jani Ollikainen for the great bug report, with
instructions on how to reproduce and even more - you basically
investigated the issue and figured it out yourself.
I'll discuss internally if the best option is to have cloud-init to
generate the netplan file in all boots (which I think makes sense) or if
we shouldn't have that "mac match" block.
Cheers,
Guilherme
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Tags added: sts
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
