Bug 2029602

Summary:	kdump: support reboot required and reboot ok
Product:	Red Hat Enterprise Linux 9	Reporter:	Rich Megginson <rmeggins>
Component:	rhel-system-roles	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED ERRATA	QA Contact:	Jakub Haruda <jharuda>
Severity:	unspecified	Docs Contact:	Jaroslav Klech <jklech>
Priority:	unspecified
Version:	9.0	CC:	djez, elpereir, gfialova, jharuda, jklech, nhosoi, spetrosi
Target Milestone:	rc
Target Release:	9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	role:kdump
Fixed In Version:	rhel-system-roles-1.11.0-1.el9	Doc Type:	Bug Fix
Doc Text:	.The Kdump RHEL System Role is be able to reboot, or indicate that a reboot is required Previously, the Kdump RHEL System Role ignored managed nodes without any reserved memory for crash kernel. Consequently, the role finished with the "Success" status, even if it did not configure the system properly. With this update of RHEL 9, the problem has been fixed. In cases when managed nodes do not have any memory reserved for the crash kernel, the Kdump RHEL System Role fails and suggests that users set the `kdump_reboot_ok` variable to `true` to properly configure the `kdump` service on managed nodes.	Story Points:	---
Clone Of:
Clones:	2029605 (view as bug list)		Environment:
Last Closed:	2022-05-17 13:03:10 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:	2029605

Description Rich Megginson 2021-12-06 21:05:06 UTC

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 22:54:29 UTC

@spetrosi can you please provide the Doc Text for this issue?

Comment 3 Rich Megginson 2021-12-07 14:43:15 UTC

Systems that have the kdump service disabled might not have memory reserved and loaded for crashkernel. Such system require enabling kdump and rebooting, hence the kdump_reboot_ok variable must be added to the kdump role

How reproducible:


Steps to Reproduce:
Run the role on the system with disabled kdump. I.e. the `/sys/kernel/kexec_crash_size` file on the system contains `0`.


Actual results:
The role either fails or passes without errors 

Expected results:
The role passes and sets the `kdump_reboot_required` fact to indicate that reboot is required. Or passes with reboot if `kdump_reboot_ok: true` is set.

Comment 4 Rich Megginson 2021-12-07 14:43:25 UTC

*** Bug 2029806 has been marked as a duplicate of this bug. ***

Comment 17 errata-xmlrpc 2022-05-17 13:03:10 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 (new packages: rhel-system-roles), 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:2443