Comment 8 for bug 1578141

I recently ran into this while upgrading 76 systems. In my research I have concluded that this bug is the result of bad information coming from the BIOS 3.0b, 3.0c, and 3.2. This bug is not present with BIOS 3.00.

If you run biosdevname, you will see that the BIOS Device name is em1 for both of the intel i350 interfaces resulting (as mentioned above by Dr. Jens Rosenboom (j-rosenboom-j) in dracut successfully naming the first device to initialize as eno1. If you reboot the system and check udevadm, you can see that the interfaces can alternate in which port is initialized first resulting in eno1 moving from port1 to port2. This is causing problems primarily with bonding our interfaces.

sudo biosdevname -d
BIOS device: em1
Kernel name: eno1
Permanent MAC: 00:00:00:00:00:00
Assigned MAC : 00:00:00:00:00:00
ifIndex: 2
Driver: igb
Driver version: 5.2.15-k
Firmware version: 1.61, 0x8000090e
Bus Info: 0000:06:00.0
PCI name : 0000:06:00.0
PCI Slot : embedded
SMBIOS Device Type: Ethernet
SMBIOS Instance: 1
SMBIOS Label: Onboard Intel Ethernet 1
sysfs Index: 1
sysfs Label: Onboard Intel Ethernet 1
Embedded Index: 1

Duplicate: True
BIOS device: em1
Kernel name: eth1
Permanent MAC: 00:00:00:00:00:00
Assigned MAC : 00:00:00:00:00:00
ifIndex: 3
Driver: igb
Driver version: 5.2.15-k
Firmware version: 1.61, 0x8000090e
Bus Info: 0000:06:00.1
PCI name : 0000:06:00.1
PCI Slot : embedded
SMBIOS Device Type: Ethernet
SMBIOS Instance: 1
SMBIOS Label: Onboard Intel Ethernet 2
sysfs Index: 1
sysfs Label: Onboard Intel Ethernet 2
Embedded Index: 2

Duplicate: True

I have submitted my findings for all of my nodes to Supermicro seeking a bug fix and releasing an update BIOS.