Bug 810651 - anaconda configure unwanted biosdevname network interfaces
anaconda configure unwanted biosdevname network interfaces
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
i686 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-04-07 14:50 EDT by Frantisek Hanzlik
Modified: 2012-04-07 22:40 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-04-07 21:28:25 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Frantisek Hanzlik 2012-04-07 14:50:00 EDT
Description of problem:
Although my kickstart file require not install biosdevname package ("-biosdevname" in ks file, it works and this package isn't installed), and "network" keyword specifies ethX interfaces with lines as:
network --onboot yes --device eth0 --bootproto static --ip --netmask --noipv6 --nameserver, --hostname janinka.resro.home

anaconda still create unwanted intefaces with bios device names (em1, pNpM).

Version-Release number of selected component (if applicable):
anaconda 16.25

How reproducible:
always when ks file specifies ethX in "network" keyword
Comment 1 Chris Lumens 2012-04-07 21:28:25 EDT
biosdevname is how network interfaces are named in Fedora now.  That's what we are going to use to name devices.
Comment 2 Frantisek Hanzlik 2012-04-07 22:40:03 EDT
biosdevnames are unfriendly and purposeless in situations, where is needed configure NICs according to their MAC addresses - which is probably still often requirement. Traditional ethN names are much better in this cases. Although is not so hard rename NIC after installation to ethN names, anaconda should be able do it as well.
(PS: anaconda F16 doc is then probably outdated, as there is nothing about biosdevnames in "network" keyword explanation, it mention ethX only. But it is other case)

Note You need to log in before you can comment on or make changes to this bug.