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:
/etc/kdump.conf has a comment that 'default halt' will halt the system, regardless of the success or failure of vmcore capture:
[root@el7a ~]# less /etc/kdump.conf
...
# default <reboot | halt | poweroff | shell | dump_to_rootfs>
...
# halt: If the default action is halt, then simply
# halt the system after attempting to capture
# a vmcore, regardless of success or failure.
This conflicts with the kdump.conf man page, which says 'default' specifies the 'Action to preform in case dumping to intended target fails':
[root@el7a ~]# man kdump.conf
...
default <reboot | halt | poweroff | shell | dump_to_rootfs>
Action to preform in case dumping to intended target fails. If no default action is specified, "reboot" is assumed default. reboot: If the default action is reboot simply reboot the system (this is what most people will want, as it returns the system to a nominal state). shell: If the default action is shell, then drop to an shell session inside the initramfs from where you can manually preform additional recovery actions. Exiting this shell reboots the system. halt: bring the system to a halt, requiring manual reset poweroff: The system will be powered down. dump_to_rootfs:If the default action is dump_to_rootfs, specified root will be mounted and dump will be saved in "path" directory. Note: kdump uses bash as the default shell.
Version-Release number of selected component (if applicable):
[root@el7a ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.2 (Maipo)
[root@el7a ~]# rpm -q kexec-tools
kexec-tools-2.0.7-38.el7.x86_64
Additional info:
Also lots of typos in /etc/kdump.conf and man kdump.conf (e.g. 'preform', 'an shell')
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://rhn.redhat.com/errata/RHEA-2016-2466.html
Description of problem: /etc/kdump.conf has a comment that 'default halt' will halt the system, regardless of the success or failure of vmcore capture: [root@el7a ~]# less /etc/kdump.conf ... # default <reboot | halt | poweroff | shell | dump_to_rootfs> ... # halt: If the default action is halt, then simply # halt the system after attempting to capture # a vmcore, regardless of success or failure. This conflicts with the kdump.conf man page, which says 'default' specifies the 'Action to preform in case dumping to intended target fails': [root@el7a ~]# man kdump.conf ... default <reboot | halt | poweroff | shell | dump_to_rootfs> Action to preform in case dumping to intended target fails. If no default action is specified, "reboot" is assumed default. reboot: If the default action is reboot simply reboot the system (this is what most people will want, as it returns the system to a nominal state). shell: If the default action is shell, then drop to an shell session inside the initramfs from where you can manually preform additional recovery actions. Exiting this shell reboots the system. halt: bring the system to a halt, requiring manual reset poweroff: The system will be powered down. dump_to_rootfs:If the default action is dump_to_rootfs, specified root will be mounted and dump will be saved in "path" directory. Note: kdump uses bash as the default shell. Version-Release number of selected component (if applicable): [root@el7a ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.2 (Maipo) [root@el7a ~]# rpm -q kexec-tools kexec-tools-2.0.7-38.el7.x86_64 Additional info: Also lots of typos in /etc/kdump.conf and man kdump.conf (e.g. 'preform', 'an shell')