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 1019104 - Interface renaming via ifname does not work for RHEL-6.5
Summary: Interface renaming via ifname does not work for RHEL-6.5
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: dracut
Version: 6.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Harald Hoyer
QA Contact: Release Test Team
URL:
Whiteboard:
: 1009718 1013158 1014123 1016827 (view as bug list)
Depends On:
Blocks: 855142 886608 917159
TreeView+ depends on / blocked
 
Reported: 2013-10-15 07:41 UTC by Harald Hoyer
Modified: 2013-11-21 21:58 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
This bug is just a regression, while developing fixes for the RHEL-6.5 erratum and does not have to have an errata doc.
Clone Of:
Environment:
Last Closed: 2013-11-21 21:58:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
iSCSI boot kernel panic (14.51 KB, image/png)
2013-10-15 07:46 UTC, IBM Bug Proxy 		no flags Details
dmesg (441.38 KB, text/plain)
2013-10-15 07:46 UTC, IBM Bug Proxy 		no flags Details
init.log with options passed (293.00 KB, text/plain)
2013-10-15 07:46 UTC, IBM Bug Proxy 		no flags Details
dmesg with rdudevinfo passed (460.50 KB, text/plain)
2013-10-15 07:46 UTC, IBM Bug Proxy 		no flags Details
init.log with rdudevinfo passed (293.00 KB, text/plain)
2013-10-15 07:46 UTC, IBM Bug Proxy 		no flags Details
Output of "udevadm test --action=add /sys/class/net/eth1" (3.07 KB, text/plain)
2013-10-15 07:47 UTC, IBM Bug Proxy 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:1674 0 normal SHIPPED_LIVE Moderate: dracut security, bug fix, and enhancement update 2013-11-20 21:52:47 UTC

Description Harald Hoyer 2013-10-15 07:41:24 UTC 
A bug in the interface renaming was introduced for dracut versions >= 004-327 and < 004-335.

This bug is not present in RHEL-6.4 dracut versions.

The udev rules /etc/udev/rules.d/50-ifname.rules had:

DRIVERS!="?*", GOTO="ifname_end"

which matched any empty string in the list of drivers for an interface.

Because there are empty strings, the correct rule should only match for positives.

DRIVERS=="?*", ....
Comment 1 Harald Hoyer 2013-10-15 07:41:55 UTC 
*** Bug 1009718 has been marked as a duplicate of this bug. ***
Comment 2 Harald Hoyer 2013-10-15 07:41:59 UTC 
*** Bug 1013158 has been marked as a duplicate of this bug. ***
Comment 3 Harald Hoyer 2013-10-15 07:42:07 UTC 
*** Bug 1014123 has been marked as a duplicate of this bug. ***
Comment 4 Harald Hoyer 2013-10-15 07:42:12 UTC 
*** Bug 1016827 has been marked as a duplicate of this bug. ***
Comment 5 IBM Bug Proxy 2013-10-15 07:46:17 UTC 
Created attachment 812379 [details]
iSCSI boot kernel panic
Comment 6 IBM Bug Proxy 2013-10-15 07:46:25 UTC 
Created attachment 812381 [details]
dmesg
Comment 7 IBM Bug Proxy 2013-10-15 07:46:35 UTC 
Created attachment 812382 [details]
init.log with options passed
Comment 8 IBM Bug Proxy 2013-10-15 07:46:44 UTC 
Created attachment 812383 [details]
dmesg with rdudevinfo passed
Comment 9 IBM Bug Proxy 2013-10-15 07:46:56 UTC 
Created attachment 812384 [details]
init.log with rdudevinfo passed
Comment 10 IBM Bug Proxy 2013-10-15 07:47:06 UTC 
Created attachment 812385 [details]
Output of "udevadm test --action=add /sys/class/net/eth1"
Comment 12 Harald Hoyer 2013-10-15 13:42:53 UTC 
http://people.redhat.com/harald/downloads/dracut/dracut-004-335.el6/
Comment 13 IBM Bug Proxy 2013-10-17 14:03:49 UTC 
------- Comment From mvechava.com 2013-10-17 13:55 EDT-------
Did this fix happen to make it into snapshot 3 or will it be added in a later release?
Comment 16 Michael Chan 2013-10-23 18:21:09 UTC 
We are testing to see if this fixes uEFI FCoE boot which doesn't work on RHEL6.5 on Broadcom NICs.
Comment 17 Eddie Wai 2013-10-24 23:17:55 UTC 
We have verified that the original reported bug for iSCSI (Bug 1013158) has been fixed with RHEL6.5ss4.

However, during the course of testing, a new iSCSI+multipath installation regression bug has been uncovered which is unrelated to this biosdevname renaming problem.

A new BZ has been created for that:
https://bugzilla.redhat.com/show_bug.cgi?id=1023225
Comment 18 Jan Stodola 2013-10-25 07:48:10 UTC 
Thank you for retesting.

Moving to VERIFIED based on comment 17.
Comment 19 IBM Bug Proxy 2013-10-25 16:21:33 UTC 
------- Comment From mvechava.com 2013-10-25 16:16 EDT-------
Snapshot 4 fixes this problem for me, as well. This bug may be closed.
Comment 20 errata-xmlrpc 2013-11-21 21:58:55 UTC 
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/RHSA-2013-1674.html
Note You need to log in before you can comment on or make changes to this bug.