VMBuilder uses eth0 when interface is actually ens3

Bug #1634300 reported by Dennis Williamson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
VMBuilder
Fix Committed
Undecided
Vacheslav Anzhiganov

Bug Description

VMBuilder (creating a 16.04 guest on a 16.04 host) uses /etc/vmbuilder/ubuntu/interfaces.tmpl to create /etc/network/interfaces. It only supports dhcp and eth0, but the actual network interface is created using Predictable Network Interface Names. As a result, the names don't match and the interface can't be brought up.

http://askubuntu.com/questions/838512/network-interface-name-mismatch-when-using-vmbuilder

Revision history for this message
Chris Puttick (cputtick) wrote :

Confirmed. Can workaround by modifying the template file and replacing instances of eth0 with ens3.

Changed in vmbuilder:
status: New → Confirmed
Changed in vmbuilder:
assignee: nobody → Vacheslav Anzhiganov (vanzhiganov)
Revision history for this message
Vacheslav Anzhiganov (vanzhiganov) wrote :

fix committed http://bazaar.launchpad.net/~vanzhiganov/vmbuilder/vmbuilder/revision/503

you can use for ubuntu xenial this file: templates/ubuntu/interfaces-xenial.tmpl

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