Bug 1029815

Summary: net.ifnames=0 don't work
Product: [Fedora] Fedora Reporter: Terje Røsten <terjeros>
Component: systemdAssignee: systemd-maint
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 20CC: johannbg, lnykryn, mschmidt, msekleta, plautrba, systemd-maint, vpavlin, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-13 12:11:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Terje Røsten 2013-11-13 09:47:39 UTC
Description of problem:

Even with net.ifnames=0 passed as kernel cmdline, systemd-udev insist on renaming
net interfaces. 

Please stop. 


systemd-208-4.fc20

Comment 1 Michal Schmidt 2013-11-13 10:22:49 UTC
net.ifnames=0 is not meant to disable the entire udev's interface renaming ability. It merely disables the udev rule that assigns interfaces the names according to the scheme described in http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

There are a few other ways your interfaces may get their names assigned:
 - by biosdevname
 - by /etc/sysconfig/network-scripts/ifcfg-* config files
 - by custom rules in /etc/udev/rules.d/

What are the exact names that you're getting?

Comment 2 Terje Røsten 2013-11-13 10:57:46 UTC
Removing biosdevname package fixed the issue. 

However, this seems messy, why the need for both systemd-udev renaming and biosdevname?

I keep disabling more and more stuff in each Fedora release...

Close ticket if you want.