Bug 1918493

Summary:	kdump initrd generation fails if /boot not writable
Product:	[Fedora] Fedora	Reporter:	Kelvin Fan <kfan>
Component:	kexec-tools	Assignee:	Kairui Song <kasong>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	33	CC:	bhe, kasong, mkarg, ruyang
Target Milestone:	---	Flags:	fedora-admin-xmlrpc: mirror+
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2003780 (view as bug list)		Environment:
Last Closed:	2021-04-28 20:38:06 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:	2003780

Description Kelvin Fan 2021-01-20 21:18:05 UTC

Description of problem:
In Fedora CoreOS versions 33.20210104.3.0 and later, the /boot directory is mounted read-only. Because of this, kdump is not 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: /boot/ostree/fedora-coreos-b75b97c31a6cd29bf45d4ba7ca6d5b5d8ee8592e909b18c3b381772a5db7e00b does not have write permission. Can not rebuild /boot/ostree/fedora-coreos-b75b97c31a6cd29bf45d4ba7ca6d5b5d8ee8592e909b18c3b381772a5db7e00b/initramfs-5.10.7-200.fc33.x86_64kdump.img

Expected results:
Crash recovery kernel arming succeeds.

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

Comment 1 Kairui Song 2021-04-28 20:38:06 UTC

Fixed in latest rawhide build.