This is a tracking bug for upstream (and will be cloned for backports) for removing the workaround keeping /boot RW for kdump support. This is essentially reverting https://bugzilla.redhat.com/show_bug.cgi?id=1971738 now that those packages are in: - https://bugzilla.redhat.com/show_bug.cgi?id=1976252 - https://bugzilla.redhat.com/show_bug.cgi?id=1976260 See: - https://github.com/coreos/fedora-coreos-config/pull/1212 - https://github.com/openshift/os/pull/622
Correction: Only 4.8+ had /boot RO.
Moving back to post for https://github.com/openshift/os/pull/632
Verified that RHCOS 410.84.202110081440-0 can enable kdump on first boot. I used the following ignition file and added karg `crashkernel=256M`. The overlay file is no longer present and kdump works as expected. { "ignition": { "version": "3.2.0" }, "passwd": { "users": [ { "name": "core", "sshAuthorizedKeys": [ "ssh-rsa AAAAB..." ] } ] }, "systemd": { "units": [ { "enabled": true, "name": "kdump.service" } ] } } [core@localhost ~]$ cat /proc/cmdline BOOT_IMAGE=(hd0,gpt3)/ostree/rhcos-2a305bb263fc7d0fb7c83f4db0123f2cf104461ef1f234c1fdef3db331097773/vmlinuz-4.18.0-305.19.1.el8_4.x86_64 random.trust_cpu=on console=tty0 console=ttyS0,115200n8 ignition.platform.id=qemu ignition.firstboot crashkernel=256M ostree=/ostree/boot.1/rhcos/2a305bb263fc7d0fb7c83f4db0123f2cf104461ef1f234c1fdef3db331097773/0 [core@localhost ~]$ sudo systemctl status kdump ● kdump.service - Crash recovery kernel arming Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; v> Active: active (exited) since Tue 2021-10-12 19:18:34 UTC; 3min 3> Process: 1307 ExecStart=/usr/bin/kdumpctl start (code=exited, stat> Main PID: 1307 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 10429) Memory: 0B CGroup: /system.slice/kdump.service Oct 12 19:18:17 localhost dracut[1633]: Stored kernel commandline: Oct 12 19:18:17 localhost dracut[1633]: rd.driver.pre=iTCO_wdt,lpc_i> Oct 12 19:18:17 localhost dracut[1633]: *** Install squash loader *** Oct 12 19:18:17 localhost dracut[1633]: *** Squashing the files insi> Oct 12 19:18:30 localhost dracut[1633]: *** Squashing the files insi> Oct 12 19:18:30 localhost dracut[1633]: *** Creating image file '/va> Oct 12 19:18:32 localhost dracut[1633]: *** Creating initramfs image> Oct 12 19:18:34 localhost kdumpctl[1307]: kdump: kexec: loaded kdump> Oct 12 19:18:34 localhost kdumpctl[1307]: kdump: Starting kdump: [OK] Oct 12 19:18:34 localhost systemd[1]: Started Crash recovery kernel > [core@localhost ~]$ ls /usr/lib/systemd/system/kdump.service.d ls: cannot access '/usr/lib/systemd/system/kdump.service.d': No such file or directory [core@localhost ~]$ sudo rpm-ostree status State: idle Deployments: ● ostree://67be3786510771cc550aa4be162f2b45cb796e4340755d7a67fa4720aa10e9ba Version: 410.84.202110081440-0 (2021-10-08T14:43:28Z)
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 (Moderate: OpenShift Container Platform 4.10.3 security 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-2022:0056
*** Bug 2063188 has been marked as a duplicate of this bug. ***