Description of problem:
When /etc/kdump.conf contains a target that is not reachable, mkdumprd bails when it tries to create the initrd.
mkdumprd will keep getting invoked every time the system reboots or the kdump service is started/restarted since the kdump.conf timestamp is greater than the kdump-initrd. This causes /tmp to start filling up with incomplete initrd builds.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. configure kdump
2. update /etc/kdump with an invalid target
3. after failure - note build remnants in /tmp
/tmp contains an incomplete initrd build
incomplete initrd builds should get cleaned out after error logging
Created attachment 331695 [details]
patch to consolidate exit cleanup in mkdumprd
hey can you give this patch a spin and confirm that it fixes your problem for me please? Thanks!
ping, any update here?
sorry - will provide update asap
entered bogus entry in kdump.conf
ran "service kdump restart"
no initrd.* left when using patched mkdumprd
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.