Bug 1965952

Summary:	[RHEL9] kdump initrd generation fails if /boot not writable
Product:	Red Hat Enterprise Linux 9	Reporter:	ltao
Component:	kexec-tools	Assignee:	ltao
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ruowen Qin <ruqin>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	cye, jieli, ruqin, xiawu
Target Milestone:	beta	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	kexec-tools-2.0.22-8.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-12-07 21:50:14 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:	1965989
Bug Blocks:

Description ltao 2021-05-31 08:32:16 UTC

Description of problem:
This bug is cloned from bz1918499

original 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

Comment 3 ltao 2021-06-23 03:40:41 UTC

brew build:

https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1642098