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.

Description of problem:
After installing RHEL7 alpha2, I noticed that the machine was not online.
I checked the interfaces configured and I see that NN has created an interface with the name "p3p1".
On the system the interface configured by udev is eth0:

# ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 16436

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

# rpm -qa | grep Netwo
NetworkManager-glib-0.9.4-3.git20120403.el7.x86_64
NetworkManager-0.9.4-3.git20120403.el7.x86_64

How reproducible:
Resinstalled the machine 2 times and I always have this issue

Steps to Reproduce:
1. Install RHEL7 with "text" option
2. Check the network configuration
  
Actual results:
No config file for the interface eth0.
A config file for the interface "p3p1" was written

Expected results:
The correct configuration file should be written

Additional info:

Is biosdevname installed?

Are there udev rules or other such things that rename the network device after it's recognized by the kernel?  biosdevname is one of these, but also see if /etc/udev/rules.d/70-persistent-net.rules exists and if that directs udev to rename your interface to eth0.

(note that NM doesn't yet handle interface name changes well after it's found the device already.  A changed name doesn't affect internal operation, but it won't be reflected in the logs or in the API.  Internally, ifindexes are what is used, and therefore the name change has no material effect)

No package biosdevname installed:

# rpm -qa | grep bios
# 

And no persistent rule in udev/rules.d:

# ls -l /etc/udev/rules.d
total 4
-rw-r--r--. 1 root root 771 May 22 14:02 90-alsa-tools-firmware.rules

If you install biosdevname, does that fix the issue?

Installing biosdevname renamed the eth0 interface to p3p1.

From where does the name p3p1 come from?

PCI slot 3, port 1.

This will be fixed in a future milestone such that biosdevname is always installed.

I believe that biosdevname and udev are fixed now such that the correct naming is happening.  NM just uses what it gets from the kernel.