Hi!
I believe this is an issue with ifupdown, rather than cloud-init. As
such, I've added an ifupdown task and marked cloud-init's task as
Invalid. If it's determined that we won't fix this in ifupdown, then
please move the cloud-init task back to New and we can consider working
around this in cloud-init.
In the meantime, you'll have to modify /etc/network/interfaces yourself
to perform the sourcing.
Thanks!
Dan
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- cloud-init configures network incorrectly on the ubuntu1804 template VM of
Azure
+ Installing ifupdown on bionic does not install a /etc/network/interfaces that
sources /etc/network/interfaces.d/*
** Changed in: cloud-init
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848617
Title:
Installing ifupdown on bionic does not install a
/etc/network/interfaces that sources /etc/network/interfaces.d/*
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1848617/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
