Installing ifupdown on bionic does not install a /etc/network/interfaces that sources /etc/network/interfaces.d/*

[ubuntu-server-builder]

This bug was originally filed in Launchpad as LP: #1848617

Launchpad details

affected_projects = ['ifupdown (Ubuntu)']
assignee = None
assignee_name = None
date_closed = 2019-10-22T15:36:39.765431+00:00
date_created = 2019-10-18T01:30:59.571032+00:00
date_fix_committed = None
date_fix_released = None
id = 1848617
importance = low
is_complete = True
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1848617
milestone = None
owner = chenxiangw
owner_name = chenxiang wang
private = False
status = invalid
submitter = chenxiangw
submitter_name = chenxiang wang
tags = []
duplicates = []

Launchpad user chenxiang wang(chenxiangw) wrote on 2019-10-18T01:30:59.571032+00:00

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.

[ubuntu-server-builder]

Launchpad user Scott Moser(smoser) wrote on 2019-10-18T13:58:43.112251+00:00

In previous ubuntu, we mostly considered it an image-creation bug if /etc/network/interfaces did not have the 'source' line you have described.

That said, is there a reason you want to have ifupdown on 18.04?

[ubuntu-server-builder]

Launchpad user Scott Moser(smoser) wrote on 2019-10-18T14:10:23.553808+00:00

Please set back to New after responding.

[ubuntu-server-builder]

Launchpad user chenxiang wang(chenxiangw) wrote on 2019-10-21T01:19:47.855172+00:00

Yes, we need to install Linux Virtual Delivery Agent (a product of Citrix) on 1804, and ifupdown is a dependency of this product. When we deploy duplicated VMs they can't get ip addresses due to this problem.

[ubuntu-server-builder]

Launchpad user Dan Watkins(oddbloke) wrote on 2019-10-22T15:36:33.197700+00:00

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