Bug 221510

Summary: kdump service should warn admins in the case that no dump directory is specified initially
Product: Red Hat Enterprise Linux 5 Reporter: Akira Imamura <aimamura>
Component: kexec-toolsAssignee: Neil Horman <nhorman>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0CC: kkomiyam, ktokunag, ntachino
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-01-04 22:11:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
This patch is based on -156.el5 and, can fix this problem. none

Description Akira Imamura 2007-01-04 21:06:36 UTC 
Description of problem:
The kdump service should warn users in the case that no dump directory
is specified initially. I think this case is one that admins need to
be aware of in advance.

Version-Release number of selected component (if applicable):
kexec-tools-1.101-156.el5

How reproducible:
Always

Steps to Reproduce:
1. Configure kdump.conf so that no dump directory is specified.
2. Run "service kdump restart"
3.
  
Actual results:
The kdump service shows no warning as below.

Stopping kdump:                                            [  OK  ]
Detected /etc/kdump.conf or /boot/efi/efi/redhat/vmlinuz-2.6.18-1.2910.el5 change
Rebuilding /boot/efi/efi/redhat/initrd-2.6.18-1.2910.el5kdump.img
Starting kdump:                                            [  OK  ]


Expected results:
The kdump service shows warning as below.

Stopping kdump:                                            [  OK  ]
Detected /etc/kdump.conf or /boot/efi/efi/redhat/vmlinuz-2.6.18-1.2910.el5 change
Rebuilding /boot/efi/efi/redhat/initrd-2.6.18-1.2910.el5kdump.img
No dump directory specified in /etc/kdump.conf             [WARNING]
Starting kdump:                                            [  OK  ]


Additional info:
Comment 1 Akira Imamura 2007-01-04 21:06:36 UTC 
Created attachment 144842 [details]
This patch is based on -156.el5 and, can fix this problem.
Comment 2 Neil Horman 2007-01-04 22:11:21 UTC 
I disagree.  Not specifying a dump location in kdump.conf is a perfectly valid
configuration (implying that the kdump initramfs should mount the root
filesystem and run init).  no warning is needed for that.