Bug 843778

Summary:	mkdumprd spits message like "no record for 'mapper/mpath0p3' in database" when dump to multipath target
Product:	Red Hat Enterprise Linux 5	Reporter:	Guangze Bai <gbai>
Component:	kexec-tools	Assignee:	Vivek Goyal <vgoyal>
Status:	CLOSED WONTFIX	QA Contact:	Guangze Bai <gbai>
Severity:	low	Docs Contact:
Priority:	low
Version:	5.8	CC:	ccui, qcai, vgoyal, yshao
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-17 02:07:04 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:
Embargoed:

Description Guangze Bai 2012-07-27 11:03:21 UTC

Description of problem:

As summary said,

# grep -v ^# /etc/kdump.conf 
ext3 /dev/mapper/mpath0p3     <--- multipath target
default shell
core_collector makedumpfile -c --message-level 1

# service kdump restart
Stopping kdump:                                            [  OK  ]
No kdump initial ramdisk found.                            [WARNING]
Rebuilding /boot/initrd-2.6.18-308.el5kdump.img
no record for 'mapper/mpath0p3' in database      <----
no record for 'mapper/mpath0p2' in database
no record for 'mapper/mpath0p3' in database
Starting kdump:                                            [  OK  ]


Version-Release number of selected component (if applicable):
kexec-tools-1.102pre-159.el5

How reproducible:
always

Expected results:
Make it a clearer message that won't confuse user.