RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

If kdump generates the dmesg log file (vmcore-dmesg.log), the vmcore's
post-create event doesn't generate 'reason' file. It is caused by
inappropriate use of 'abrt-dump-oops' where the event uses that helper
to parse the log file to generate 'backtrace' file instead of using it
with the '-u' argument to update the dump directory and create all
necessary files.

Additional info:
Easy fix, this upstream commit fixes the issue:
https://github.com/abrt/abrt/commit/7800a01bd0d7fa6e53564fc4394f126f2042775f

Upstream commit fixes the issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1166633

Related upstream testcase:
https://github.com/abrt/abrt/pull/1138/commits/42f7c0bcebd5984430cb6b0cff77683813d94dc3

Created attachment 1153721 [details]
Patch 1/1: vmcore: generate 'reason' file in all cases

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, 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://rhn.redhat.com/errata/RHBA-2016-2307.html