Comment 17 for bug 1982582
Revision history for this message
| bugproxy (bugproxy) wrote Comment bridged from LTC Bugzilla | #17 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
------- Comment From <email address hidden> 2022-12-16 08:38 EDT-------
I was also able to successfully verify unattended installation of kdump-tools 1:1.6.10ubuntu2.1 on jammy
However - but this might be a separate issue - there is not value for crashkernel memory set (which makes no sense and prevents kdump from dumping:
root@a3515006:~# systemctl status kdump-tools
? kdump-tools.service - Kernel crash dump capture service
Loaded: loaded (/lib/systemd/
Active: active (exited) since Fri 2022-12-16 13:16:35 UTC; 3min 13s ago
Process: 14751 ExecStart=
Main PID: 14751 (code=exited, status=0/SUCCESS)
CPU: 12ms
Dec 16 13:16:35 a3515006.lnxne.boe systemd[1]: Starting Kernel crash dump capture service...
Dec 16 13:16:35 a3515006.lnxne.boe kdump-tools[14751]: Starting kdump-tools:
Dec 16 13:16:35 a3515006.lnxne.boe kdump-tools[14756]: * no crashkernel= parameter in the kernel cmdline
Dec 16 13:16:35 a3515006.lnxne.boe systemd[1]: Finished Kernel crash dump capture service.
root@a3515006:~# cat /proc/cmdline
root=/dev/
root@a3515006:~# cat /etc/zipl.conf
# This has been modified by the MAAS curtin installer
[defaultboot]
default=ubuntu
[ubuntu]
target = /boot
image = /boot/vmlinuz
ramdisk = /boot/initrd.img
parameters = root=/dev/
root@a3515006:~#
The installation didn't set a crashkernel value in /etc/zipl.conf (like focal was doing). A triggered panic didn't create a kdump, unless I set the crashkernel parameter appropriately and rebooted.