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.
DDESCRIPTION:
------------
During the ixgbe reload stress test, a new duplicated entry is added to the 70-persistent-net.rules file located (/etc/udev/rules.d/70-persistent-net.rules). The newly added interface (eth4) has the same MAC address as a currently existing interface (eth3).
Syslog reports that udev renamed eth3 to eth4:
Apr 3 03:29:14 linstd49 kernel: udev: renamed network interface eth3 to eth4
udevd-work[13866]: error changing netif name 'eth3' to 'eth4': No such device
These events are repeated in syslog through the stress test.
# PCI device 0x8086:0x1096 (e1000e) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:30:48:7f:26:ce", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# PCI device 0x8086:0x10fb (ixgbe) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:21:55:23:b1", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"
# PCI device 0x8086:0x10fb (ixgbe) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:21:55:23:b0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
# PCI device 0x8086:0x1096 (e1000e) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:30:48:7f:26:cf", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
# PCI device 0x8086:0x10fb ()
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:21:55:23:b1", KERNEL=="eth*", NAME="eth4"
There is no 5th interface (eth4) on the system, it was added erroneously during heavy ixgbe stress.
CONFIGURATION:
------------
Test Configuration:
Supermicro (System ID 14499),1 quad-core CPU, 8 GB RAM, dual-port Niantic, RHEL6.0-GA-x86_64 + errata updates
STEPS TO REPRODUCE:
-------------------
1.) while true ; do
rmmod ixgbe ; modprobe ixgbe ;
done
RESULTS:
---------
Duplicate MAC address is used for a new eth4 entry in the 70-persistent-net.rules file. No eth4 exists on the system. The entry has the same mac as an already existing entry, eth3.
EXPECTED RESULTS:
----------------
No new udev rules should be created or renamed for already existent ethernet interface/MAC address pairs in the 70-persistent-net.rules file.This appears to be Udev related.
Comment 2RHEL Program Management
2011-04-23 06:00:28 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
DDESCRIPTION: ------------ During the ixgbe reload stress test, a new duplicated entry is added to the 70-persistent-net.rules file located (/etc/udev/rules.d/70-persistent-net.rules). The newly added interface (eth4) has the same MAC address as a currently existing interface (eth3). Syslog reports that udev renamed eth3 to eth4: Apr 3 03:29:14 linstd49 kernel: udev: renamed network interface eth3 to eth4 udevd-work[13866]: error changing netif name 'eth3' to 'eth4': No such device These events are repeated in syslog through the stress test. # PCI device 0x8086:0x1096 (e1000e) (custom name provided by external tool) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:30:48:7f:26:ce", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" # PCI device 0x8086:0x10fb (ixgbe) (custom name provided by external tool) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:21:55:23:b1", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3" # PCI device 0x8086:0x10fb (ixgbe) (custom name provided by external tool) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:21:55:23:b0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2" # PCI device 0x8086:0x1096 (e1000e) (custom name provided by external tool) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:30:48:7f:26:cf", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" # PCI device 0x8086:0x10fb () SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:21:55:23:b1", KERNEL=="eth*", NAME="eth4" There is no 5th interface (eth4) on the system, it was added erroneously during heavy ixgbe stress. CONFIGURATION: ------------ Test Configuration: Supermicro (System ID 14499),1 quad-core CPU, 8 GB RAM, dual-port Niantic, RHEL6.0-GA-x86_64 + errata updates STEPS TO REPRODUCE: ------------------- 1.) while true ; do rmmod ixgbe ; modprobe ixgbe ; done RESULTS: --------- Duplicate MAC address is used for a new eth4 entry in the 70-persistent-net.rules file. No eth4 exists on the system. The entry has the same mac as an already existing entry, eth3. EXPECTED RESULTS: ---------------- No new udev rules should be created or renamed for already existent ethernet interface/MAC address pairs in the 70-persistent-net.rules file.This appears to be Udev related.