Red Hat Bugzilla – Bug 810107
Kdump can't use a renamed NIC for remote dump.
Last modified: 2013-05-27 02:12:54 EDT
Description of problem:
In first kernel, udev rule may rename an NIC from eth0 to em1. In this case when building kdump image, 99kdumpbase/module-setup.sh will record em1 in /etc/cmdline.d/40ip.conf in the kdump initramfs.
But on second kernel, we don't have that renaming udev rule, so the original NIC will appear to be eth0 ( not renamed to be em1). Because we have configured kdump to use em1 when building kdump image, and we don't have em1 on second kernel, dump to a remote target will fail.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
On first kernel booting:
[ 25.221669] igb 0000:01:00.0: eth0: (PCIe:2.5Gb/s:Width x4) 00:15:17:a2:71:b4
[ 25.229718] igb 0000:01:00.0: eth0: PBA No: 1040FF-0FF
[ 25.235470] igb 0000:01:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)
[ 25.244172] igb 0000:01:00.1: PCI INT A -> GSI 28 (level, low) -> IRQ 28
[ 25.680989] udevd: renamed network interface eth0 to em1
On second kernel, udevd won't rename the NIC name.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.