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.
Cause:
rename_device.c does not cope with VLAN interfaces.
Consequence:
The physical interface can be improperly named.
Fix:
Check for VLANs in rename_device.c
Result:
Interfaces are named properly.
Description of problem:
If the /etc/sysconfig/network-scripts/ifcfg-eth0.123 file contains a HWADDR declaration, the physical interface can improperly named eth0.123 instead of eth0.123. It would be nice for udev to ignore VLAN interface configurations entirely.
Sample configuration that would cause problems:
DEVICE=eth2.50
HWADDR=00:15:17:0B:49:B4
ONBOOT=yes
TYPE=Ethernet
IPADDR=10.50.0.1
NETMASK=255.255.0.0
VLAN=yes
Agreed. Here's a conversation on #udev from back in July...
[11:04am] haraldh: Norm, pong
[11:04am] Norm: i had a RHEL question regarding udev naming interfaces using a subinterface name (eth0.14) instead of the real name (eth0), but i'm suspecting it may be due to my specifying HWADDR in ifcfg-eth0 and in ifcfg-eth0.14
[11:05am] haraldh: ouch
[11:05am] haraldh: please do not do that in ifcfg-eth0.14
[11:06am] Norm: hehe
[11:06am] Norm: let me tell you, when udev names your interface "eth0.14", you're in for a world of hurt
[11:06am] haraldh: true
[11:07am] Norm: this is a RHEL5 -> RHEL6 upgrade, in previous versions it was equally unnecessary, but didn't hurt anything
[11:07am] haraldh: mmhh.. yes
[11:07am] Norm: anyway, i'm hopeful that this reboot will straighten everything out
[11:07am] haraldh: Norm, can you open a bugzilla for this?
[11:07am] Norm: sure thing
[11:07am] haraldh: so I will not forget
[11:07am] haraldh: thank you!
[11:07am] Norm: np, thank you!
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-0518.html