Networking packages are not installed into the target

Bug #1491994 reported by Blake Rouse
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
curtin
Fix Released
Critical
Ryan Harper

Bug Description

The following packages should be installed into the target Ubuntu from curtin when the custom networking configuration requires them for that networking configuration to take affect.

vlan - VLANs
ifenslave - Bonds
bridge-utils - Bridges

Without this the systems will fail to boot and will fail to configure networking correctly.

Related branches

Ryan Harper (raharper)
Changed in curtin:
assignee: nobody → Ryan Harper (raharper)
Revision history for this message
Ryan Harper (raharper) wrote :

Should be fixed in lp:~raharper/curtin/fix-network-package-install

but I don't have the vmtest fully working; partly because I need to figure out a working bonding configuration to verify things. However, the branch does handle ensuring the correct packages are installed in target.

Revision history for this message
Ryan Harper (raharper) wrote :

Sorry for the longer time to land. Beyond the package installs, there were a number of issues w.r.t the bonding config generation, so this branch will also resolve those issues as well. As soon as testing passes, I can commit to trunk.

Revision history for this message
Ryan Harper (raharper) wrote :

Applied to trunk.

Changed in curtin:
status: Triaged → Fix Committed
Revision history for this message
Scott Moser (smoser) wrote : Fixed in Curtin 17.1

This bug is believed to be fixed in curtin in 17.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in curtin:
status: Fix Committed → Fix Released
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.