Verified with 4.10 ztp. [core@master-2 ~]$ cat /proc/cmdline BOOT_IMAGE=(hd0,gpt3)/ostree/rhcos-1c203921981615cc7c6ac73a7a7fd5ad40c72f3c1ea11fad613995a2b93564c7/vmlinuz-4.18.0-305.40.2.rt7.113.el8_4.x86_64 random.trust_cpu=on console=tty0 console=ttyS0,115200n8 ignition.platform.id=metal ostree=/ostree/boot.1/rhcos/1c203921981615cc7c6ac73a7a7fd5ad40c72f3c1ea11fad613995a2b93564c7/0 ip=eno1:dhcp root=UUID=70495d0b-0594-46e4-ac47-cb850ed31773 rw rootflags=prjquota boot=UUID=33a2b178-0565-46cf-87f1-48834eded96a crashkernel=256M skew_tick=1 nohz=on rcu_nocbs=2-39,42-79 tuned.non_isolcpus=00000300,00000003 intel_pstate=disable nosoftlockup tsc=nowatchdog intel_iommu=on iommu=pt isolcpus=managed_irq,2-39,42-79 systemd.cpu_affinity=0,1,40,41 default_hugepagesz=1G hugepagesz=1G hugepages=32 idle=poll rcupdate.rcu_normal_after_boot=0 nohz_full=2-39,42-79
Also verified it actually works: [root@master-2 core]# echo c > /proc/sysrq-trigger [root@master-2 core]# ls -l /var/crash/ total 0 drwxr-xr-x. 2 root root 67 Mar 23 16:33 127.0.0.1-2022-03-23-16:33:06
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 (OpenShift Container Platform 4.10.22 extras 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/RHBA-2022:5514