system-config-kickstart only allows eth0 etc...

Bug #1591134 reported by Paul Hewlett on 2016-06-10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
system-config-kickstart (Ubuntu)

Bug Description

Ethernet devices are now persistently named as enp3s0 etc.

This package only allows selecting ethernet devices named eth0 etc...

paul@galileo:~$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04

paul@galileo:~$ apt-cache policy system-config-kickstart
  Installed: 2.5.20-0ubuntu25
  Candidate: 2.5.20-0ubuntu25
  Version table:
 *** 2.5.20-0ubuntu25 500
        500 xenial/main amd64 Packages
        500 xenial/main i386 Packages
        100 /var/lib/dpkg/status


    able to select enp3s0 as network device

What happened:

    only able to select eth0 etc from dropdown dialog

affects: atftp (Ubuntu) → system-config-kickstart (Ubuntu)
Jb (jebsolutions) wrote :

For me, if I have one network device it magically maps to eth0 and it works.

However, if there are more than Ethernet devices then nothing is mapped to eth0 and it doesn't work. And by doesn't work, I mean the installer crashes.

To duplicate just set to eth0 in kickstart and boot a VirtualBox virtual machine with two Intel Ethernet adapters.

Work around is to manually edit the kickstart file:

Original line:
network --bootproto=dhcp --device=eth0

fixed line:
network --bootproto=dhcp --device=auto

Jb (jebsolutions) wrote :

However, if there are more than _one_ Ethernet devices then nothing is...

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers