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:
The /boot directory in RHEL CoreOS will soon be mounted read-only after version 4.7. Because of this, kdump will not be able to place the generated kdump initrd next to the kernel image in `KDUMP_BOOTDIR`. 
Possible solutions would be to make the location of the generated kdump initrd configurable, or to remount /boot writable whenever kdump needs to write to it. 

How reproducible:
Always

Steps to Reproduce:
1. systemctl start kdump.service

Actual results:
kdump does not have permission to write to the /boot directory so it cannot build the kdump initramfs.

Expected results:
Crash recovery kernel arming succeeds.

Additional info:
https://issues.redhat.com/browse/GRPA-3209

Patch v2 is still in review in fc upstream:

https://lists.fedoraproject.org/archives/list/kexec@lists.fedoraproject.org/message/73XGH3N7GQS5LCNTUNQQ6NREKLBUCJH6/

patch v3 has been merged in fedora:

https://lists.fedoraproject.org/archives/list/kexec@lists.fedoraproject.org/thread/G5LMDXOA46A7AXGQIXPZ3XU65H52D4I4/

The v3 patch is ready for merge into rhel, however, there is a selinux problem [1] which need to be fixed first.

The initramfs can be created in /var/lib/kdump successfully by v3 patch, but the selinux policy refuses kexec-tools to load it,
thus fails the kdump arming. So this bug is blocked by bz1951323

[1] https://github.com/fedora-selinux/selinux-policy/issues/727

On Fedora-Rawhide-20210529.n.0, patch v3 tested can work. May need to backport [1] to rhel8 first, to make patch v3 work on rhel8.

[1] https://github.com/fedora-selinux/selinux-policy/pull/732

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

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

Clearing needinfo as AFAIU Kelvin completed the request.

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 (Low: kexec-tools security, 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/RHSA-2021:4404