Description of problem: kill -SIGSEGV [PID] for qemu process should generate core structure under abrt configured directory when the system configured properly. ls /var/tmp/abrt ccpp-2017-11-12-17:29:39-18108 ccpp-2017-11-15-16:19:01-3843 last-ccpp In current version qemu processes are set with "max core file size 0" - which leads to no output at all. If system is set with "ulimit -c unlimited" you will get the dumps. by default the os installations configured with that value set to 0, unless the process itself configured it, it will inherit the system value. Version-Release number of selected component (if applicable): v4.20.7 How reproducible: 100% Steps to Reproduce: 1. run vm and kill its pid 2. check coredump output under /var/tmp/abrt Actual results: no core dumps output Expected results: qemu process core limit set to unlimited, and coredumps are generated under abrt folder
Setting as a blocker for 4.1.8 now, we need to find out since when qemu coredumps are not available.
Moving to 4.1.9 as we will need more time to provide fix especially around the upgrade. Also removing blocker flag as this doesn't affect normal flows, it just affects our ability to analyze issues, when coredumps (and that means also stacktraces for abort) are not created
I posted https://gerrit.ovirt.org/84540 that raises the conf version, this will force re-configure on upgrade. I'm not sure we want to backport this to 4.1 to avoid running re-configure (which involve also restart of libvirt) during minor version upgrade. introduce it in 4.2 will force re-configure during upgrade which I think is more appropriate if its not a regression. Do you agree?
Without this change, abrt doesn't produce any output on kill. With this fix the following will be generated: [root@dhcp-0-135 vdsm]# kill -SIGSEGV 21662 [root@dhcp-0-135 vdsm]# cd /var/tmp/abrt/ [root@dhcp-0-135 abrt]# ls ccpp-2017-11-23-15:53:15-21662 last-ccpp [root@dhcp-0-135 abrt]# cd ccpp-2017-11-23-15\:53\:15-21662/ [root@dhcp-0-135 ccpp-2017-11-23-15:53:15-21662]# ll total 216 -rw-r-----. 1 root abrt 6 Nov 23 15:53 abrt_version -rw-r-----. 1 root abrt 4 Nov 23 15:53 analyzer -rw-r-----. 1 root abrt 6 Nov 23 15:53 architecture -rw-r-----. 1 root abrt 724 Nov 23 15:53 cgroup -rw-r-----. 1 root abrt 3119 Nov 23 15:53 cmdline -rw-r-----. 1 root abrt 11 Nov 23 15:53 component -rw-r-----. 1 root abrt 1 Nov 23 15:53 count -rw-r-----. 1 root abrt 7933 Nov 23 15:53 dso_list -rw-r-----. 1 root abrt 85 Nov 23 15:53 environ -rw-r-----. 1 root abrt 0 Nov 23 15:53 event_log -rw-r-----. 1 root abrt 21 Nov 23 15:53 executable -rw-r-----. 1 root abrt 5 Nov 23 15:53 global_pid -rw-r-----. 1 root abrt 25 Nov 23 15:53 hostname -rw-r-----. 1 root abrt 25 Nov 23 15:53 kernel -rw-r-----. 1 root abrt 10 Nov 23 15:53 last_occurrence -rw-r-----. 1 root abrt 1323 Nov 23 15:53 limits -rw-r-----. 1 root abrt 135 Nov 23 15:53 machineid -rw-r-----. 1 root abrt 57208 Nov 23 15:53 maps -rw-r-----. 1 root abrt 6359 Nov 23 15:53 open_fds -rw-r-----. 1 root abrt 393 Nov 23 15:53 os_info -rw-r-----. 1 root abrt 37 Nov 23 15:53 os_release -rw-r-----. 1 root abrt 30 Nov 23 15:53 package -rw-r-----. 1 root abrt 5 Nov 23 15:53 pid -rw-r-----. 1 root abrt 6 Nov 23 15:53 pkg_arch -rw-r-----. 1 root abrt 2 Nov 23 15:53 pkg_epoch -rw-r-----. 1 root abrt 19 Nov 23 15:53 pkg_fingerprint -rw-r-----. 1 root abrt 11 Nov 23 15:53 pkg_name -rw-r-----. 1 root abrt 12 Nov 23 15:53 pkg_release -rw-r-----. 1 root abrt 6 Nov 23 15:53 pkg_vendor -rw-r-----. 1 root abrt 5 Nov 23 15:53 pkg_version -rw-r-----. 1 root abrt 1180 Nov 23 15:53 proc_pid_status -rw-r-----. 1 root abrt 1 Nov 23 15:53 pwd -rw-r-----. 1 root abrt 26 Nov 23 15:53 reason -rw-r-----. 1 root abrt 4 Nov 23 15:53 runlevel -rw-r-----. 1 root abrt 10 Nov 23 15:53 time -rw-r-----. 1 root abrt 4 Nov 23 15:53 type -rw-r-----. 1 root abrt 3 Nov 23 15:53 uid -rw-r-----. 1 root abrt 5 Nov 23 15:53 username -rw-r-----. 1 root abrt 40 Nov 23 15:53 uuid -rw-r-----. 1 root abrt 1256 Nov 23 15:53 var_log_messages
Verified on vdsm-4.19.41-1.el7ev.x86_64