Due to a recent update on Javascript code a full page refresh on your browser might be needed.

Bug 1366513

Summary: kdump doesn't handle DEV_ID properly for the network interface mapping cases
Product: Red Hat Enterprise Linux 6 Reporter: Xunlei Pang <xlpang>
Component: kexec-toolsAssignee: Xunlei Pang <xlpang>
Status: CLOSED ERRATA QA Contact: Emma Wu <xiawu>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.9CC: bhe, ccui, cye, kdump-team-bugs, xiawu, xlpang
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: kexec-tools-2.0.0-304.el6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-21 09:12:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Xunlei Pang 2016-08-12 07:45:17 UTC
Description of problem:
On system with multiple network interfaces, if kdump does the interface mapping,
it will throw:
cat: can't open '/sys/class/net/eth1/dev_id': No such file or directory

Actually there's only eth0 in kdump kernel, eth1 is the old interface in the first kernel.

Normally, this has no problem, but for multiport network card with no "HWADDR" directive specified in ifcfg files, it will rely on DEV_ID to do the matching, and thus problematic.

Version-Release number of selected component (if applicable):
Release 2.0.0-300

How reproducible:


Steps to Reproduce:
1. Using system with multiple network cards installed.
2. Configure to use network dumping via eth1 for example
3. rebuild initramfs and trigger a crash

Actual results:
cat: can't open '/sys/class/net/eth1/dev_id': No such file or directory

Expected results:
No warning printed, and the network dumping can work properly.

Additional info:

Comment 14 errata-xmlrpc 2017-03-21 09:12:50 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.

https://rhn.redhat.com/errata/RHBA-2017-0584.html