Bug 1918493 - kdump initrd generation fails if /boot not writable
Summary: kdump initrd generation fails if /boot not writable
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kexec-tools
Version: 33
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kairui Song
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2003780
TreeView+ depends on / blocked
 
Reported: 2021-01-20 21:18 UTC by Kelvin Fan
Modified: 2021-09-13 16:58 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
: 2003780 (view as bug list)
Environment:
Last Closed: 2021-04-28 20:38:06 UTC
Type: Bug
Embargoed:
fedora-admin-xmlrpc: mirror+

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.