Bug 1752062

Summary: Correction in the man page of kdump.conf
Product: Red Hat Enterprise Linux 8 Reporter: Ashok Kumar Pathakamuri <apathaka>
Component: kexec-toolsAssignee: lijiang
Status: CLOSED ERRATA QA Contact: Emma Wu <xiawu>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: ruyang, xiawu
Target Milestone: rcKeywords: ManPageChange
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: kexec-tools-2.0.20-4.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1752724 (view as bug list) Environment:
Last Closed: 2020-04-28 16:43:23 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:
Bug Depends On:    
Bug Blocks: 1732733, 1752724, 1755139    

Description Ashok Kumar Pathakamuri 2019-09-13 15:15:57 UTC
Description of problem:

There is one opportunity of a correction in man page of kdump.conf.

1. Snippet from man page of kdump.conf:

--------------

       blacklist <list of kernel modules>
              blacklist  option  was  recently  being  used to prevent loading modules in initramfs. General terminology for blacklist has been that module is present in initramfs but it is not actually
              loaded in kernel. Hence retaining blacklist option creates more confusing behavior. It has been deprecated.

              Instead, use rd.driver.blacklist option on second kernel to blacklist a certain module. One can edit /etc/sysconfig/kdump.conf and edit KDUMP_COMMANDLINE_APPEND to pass kernel command line
              options. Refer to dracut.cmdline man page for more details on module blacklist option.

--------------

Here, mentioned file name is /etc/sysconfig/kdump.conf. Expected file name is '/etc/sysconfig/kdump'.


Additional Information:

It is same on all minor versions RHEL 7 as well.

Comment 4 errata-xmlrpc 2020-04-28 16:43:23 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://access.redhat.com/errata/RHBA-2020:1783