Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
system-config-kdump got error core_collector information, since kexec-tools update to 2.0.4-15.el7 after, use lzo by default as makedumpfile compression method, but s-c-kdump still use "CORE_COLLECTOR_DEFAULT = "makedumpfile -c".
Version-Release number of selected component (if applicable):
system-config-kdump-2.0.13-4.el7.noarch
kexec-tools-2.0.4-18.el7
How reproducible:
alwanys
Steps to Reproduce:
1. Install kexec-tools and system-config-kdump
2. Use default kdump.conf and start kdump.service
3. Start system-config-kdump and click "Expert settings"
Actual results:
Core collector is "makedumpfile -c -d 31"
Expected results:
Core collector is "makedumpfile -c -d 31" if kexec-tools version less than 2.0.4-15
Core collector is "makedumpfile -l -d 31" if kexec-tools great than or equal to 2.0.5-15
Additional info:
system-config-kdump-2.0.13/src/system-config-kdump.py
87 PATH_DEFAULT = "/var/crash"
88 CORE_COLLECTOR_DEFAULT = "makedumpfile -c"
89 FILTER_LEVEL_DEFAULT = 31
(In reply to Martin Milata from comment #1)
> Is it safe to make LZO the default for Fedora as well?
It's already done in F19 and F20 (kexec-tools-2.0.4-18)
Created attachment 853388[details]
Proposed patch
Since at least kexec-tools-2.0.4-20.el7 (version in today's compose), kdump.conf includes the default core_collector directive uncommented and system-config-kdump uses that instead of its hardcoded value.
Either way, I'm going to commit the attached patch for the case when the user has kdump.conf without core_collector directive for some reason.
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.