ifupdown does not render viable /etc/network/interfaces on bionic ec2 cloud-images

Bug #1868329 reported by Chad Smith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ifupdown (Ubuntu)
New
Undecided
Unassigned
Bionic
New
Undecided
Unassigned
Eoan
Won't Fix
Undecided
Unassigned
Focal
New
Undecided
Unassigned

Bug Description

Filing this bug for clarification and tracking on Ubuntu Bionic and later.

Canonical cloudimages for Ec2 and other clouds leave an artifact that disables /etc/network/interface with the following content:

# ifupdown has been replaced by netplan(5) on this system. See
# /etc/netplan for current configuration.
# To re-enable ifupdown on this system, you can run:
# sudo apt install ifupdown

In following the suggested text, installing the ifupdown deb continues to leave a broken system because ifupdown.postinst script creates an /etc/network/interfaces.d parts directory but does not write out a working /etc/network/interfaces file if the file exists on the system.

This leaves a broken /etc/network/interfaces files which doesn't source /etc/network/interfaces.d/* and 3rd parties cannot use the interfaces.d parts directory to extend networking config.

Cloud-init is one of those users of /etc/network/interfaces.d/ for rendering system networking on cloud images. Per LP: #1867029

I have attached ifupdwown-test.sh which exercises this issue on lxc by mocking the CPC cloudimage artifact.

Tags: uec-images
Chad Smith (chad.smith)
description: updated
Revision history for this message
Chad Smith (chad.smith) wrote :
description: updated
Revision history for this message
Brian Murray (brian-murray) wrote :

The Eoan Ermine has reached end of life, so this bug will not be fixed for that release

Changed in ifupdown (Ubuntu Eoan):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.