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 Touch seeded packages, which is subscribed to ifupdown in 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/* Status in cloud-init: Invalid Status in ifupdown package in Ubuntu: New Bug description: For the ubuntu1804 template VM of Azure, the file /etc/network/interfaces lacks a line: source /etc/network/interfaces.d/* So the VM can't get configurations under /etc/network/interfaces.d/ After installing ifupdown on the VM, cloud-init will rewrite file /etc/network/interfaces.d/50-cloud-init.cfg rather than /etc/netplan/50-cloud-init.yaml, but /etc/network/interfaces.d/50-cloud-init.cfg won't take effect. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1848617/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp