Red Hat Bugzilla – Bug 1019104
Interface renaming via ifname does not work for RHEL-6.5
Last modified: 2013-11-21 16:58:55 EST
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:
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.
*** Bug 1009718 has been marked as a duplicate of this bug. ***
*** Bug 1013158 has been marked as a duplicate of this bug. ***
*** Bug 1014123 has been marked as a duplicate of this bug. ***
*** Bug 1016827 has been marked as a duplicate of this bug. ***
Created attachment 812379 [details]
iSCSI boot kernel panic
Created attachment 812381 [details]
Created attachment 812382 [details]
init.log with options passed
Created attachment 812383 [details]
dmesg with rdudevinfo passed
Created attachment 812384 [details]
init.log with rdudevinfo passed
Created attachment 812385 [details]
Output of "udevadm test --action=add /sys/class/net/eth1"
------- Comment From email@example.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?
We are testing to see if this fixes uEFI FCoE boot which doesn't work on RHEL6.5 on Broadcom NICs.
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:
Thank you for retesting.
Moving to VERIFIED based on comment 17.
------- Comment From firstname.lastname@example.org 2013-10-25 16:16 EDT-------
Snapshot 4 fixes this problem for me, as well. This bug may be closed.
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.