Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1399813

Summary:	Enabling biosdevname has not effect
Product:	Red Hat Enterprise Linux 7	Reporter:	David Jones <david.jones74>
Component:	biosdevname	Assignee:	Michal Sekletar <msekleta>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.2
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-31 14:36:59 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:
Embargoed:

Description David Jones 2016-11-29 19:22:42 UTC

Description of problem:
I have a net-booted image created from RHEL 7.2 minimal, that boots via pxelinux. Because it's a minimal install, consistent interface naming is not enabled. Enabling it using the kernel parameters has no effect.


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


How reproducible:
Always


Steps to Reproduce:
1. Append "biosdevname=1 net.ifname=0" to the PXE kernel options
2. Boot the system from the image. 
3. Run "ip addr" to to check interface names. 

Actual results:
Interface names use "ethX" convention.

Expected results:
Interface names should follow biosdevname.


Additional info:

I've confirmed that biosdevname is installed, and am able to determine the "BIOS device" name using "biosdevname -d". 

I've confirmed that the kernel command line parameters are correct using "cat /proc/cmdline". 

The systemd-networkd service is being used to manage the network, and configure the interfaces. But there are no renaming rules.

Comment 2 Michal Sekletar 2016-12-05 13:56:14 UTC

I will need more data to determine why biosdevname naming scheme is not applied. sos_report would be ideal. If you can't attach sos_report, than gather at least output of the following tools: 

- biosdevname -d
- udevadm test --action=add /sys/class/net/eth0
- dmidecode
- lspci -vvv