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.
Bug 2029605 - kdump: support reboot required and reboot ok
Summary: kdump: support reboot required and reboot ok
Keywords:
Status: CLOSED ERRATA
Alias: None
Deadline: 2021-12-07
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rhel-system-roles
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.6
Assignee: Rich Megginson
QA Contact: David Jež
Gabi Fialová
URL:
Whiteboard: role:kdump
: 2029804 (view as bug list)
Depends On: 2029602
Blocks: 2029806
TreeView+ depends on / blocked
 
Reported: 2021-12-06 21:07 UTC by Rich Megginson
Modified: 2022-05-10 14:39 UTC (History)
5 users (show)

Fixed In Version: rhel-system-roles-1.11.0-1.el8
Doc Type: Bug Fix
Doc Text:
.The Kdump System Role does not ignore hosts anymore Previously, the Kdump role ignored managed nodes that do not have memory reserved for crash kernel, and consequently completed with the “Success” status even when not configuring the system correctly. The role has been redesigned to fail in cases where managed nodes do not have memory reserved for crash kernel, and to prompt the user to set the `kdump_reboot_ok` variable to `true` to correctly configure kdump on managed nodes. As a result, the Kdump role now does not ignore hosts, and either completes successfully with the correct configuration, or fails with an error message describing what users need to do to fix the issue.
Clone Of: 2029602
Environment:
Last Closed: 2022-05-10 14:12:46 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github linux-system-roles kdump pull 84 0 None Merged Add reboot required 2021-12-06 21:07:38 UTC
Red Hat Issue Tracker RHELPLAN-104909 0 None None None 2021-12-06 21:13:48 UTC
Red Hat Product Errata RHBA-2022:1896 0 None None None 2022-05-10 14:13:12 UTC

Description Rich Megginson 2021-12-06 21:07:39 UTC 
+++ This bug was initially created as a clone of Bug #2029602 +++

Description of problem:
kdump role should be able to reboot the node when necessary, and the user should be able to control when the node is rebooted.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Rich Megginson 2021-12-06 23:06:24 UTC 
@spetrosi please provide Doc Text for this
Comment 3 Rich Megginson 2021-12-07 14:41:25 UTC 
*** Bug 2029804 has been marked as a duplicate of this bug. ***
Comment 14 errata-xmlrpc 2022-05-10 14:12:46 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 (rhel-system-roles bug fix and enhancement update), 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-2022:1896
Note You need to log in before you can comment on or make changes to this bug.