Bug 1250337

Summary: Generate 'reason' file from dmesg log file
Product: Red Hat Enterprise Linux 7 Reporter: Matej Habrnal <mhabrnal>
Component: abrtAssignee: abrt <abrt-devel-list>
Status: CLOSED ERRATA QA Contact: Martin Kyral <mkyral>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: jberan, jfilak, mkyral
Target Milestone: rcKeywords: EasyFix, Patch
Target Release: 7.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: abrt-2.1.11-39.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 03:06:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Patch 1/1: vmcore: generate 'reason' file in all cases none

Description Matej Habrnal 2015-08-05 07:55:22 UTC 
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
Comment 2 Matej Habrnal 2016-05-02 14:55:23 UTC 
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
Comment 4 Matej Habrnal 2016-05-04 07:25:55 UTC 
Created attachment 1153721 [details]
Patch 1/1: vmcore: generate 'reason' file in all cases
Comment 7 errata-xmlrpc 2016-11-04 03:06:11 UTC 
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