Bug 1123262

Summary:	[Regression] satyr generates DUPHASH value for koopses consisting only from unreliable frames
Product:	Red Hat Enterprise Linux 7	Reporter:	Jakub Filak <jfilak>
Component:	satyr	Assignee:	Martin Milata <mmilata>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Zachar <lzachar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.1	CC:	jberan
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	satyr-0.13-5.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-05 13:26:45 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:

Description Jakub Filak 2014-07-25 07:52:32 UTC

Description of problem:
satyr does not find any reliable frame for hashing and generates the hash value from empty string. ABRT uses the hash value to identify duplicates in Bugzilla, so it means that all unreliable oopses are reported as a single Bugzilla bug. However, that koopses should not be reported at all. In order to fix this issue, satyr must return NULL from the hashing function for unreliable koopses.

Version-Release number of selected component (if applicable):
abrt-2.1.11-12.el7

Additional info:
Upstream commit https://github.com/abrt/satyr/commit/d818117a985ed5bdd00eafbc6ef9ce3f9ec54c58 fixes this bug.

Comment 2 Martin Milata 2014-09-17 14:14:13 UTC

*** Bug 1142342 has been marked as a duplicate of this bug. ***

Comment 5 Jakub Filak 2014-11-14 13:09:08 UTC

The upstream patch includes a test case:
https://github.com/abrt/satyr/commit/d818117a985ed5bdd00eafbc6ef9ce3f9ec54c58

ABRT tests satyr's ability to recognize an unreliable oops in 'Drop unreliable OOPS' phase of 'oops-processing' integration test[1] ('oops_no_reliable_frame' file [2]).

1: https://github.com/abrt/abrt/tree/master/tests/runtests/oops-processing
2: https://github.com/abrt/abrt/blob/master/examples/oops_no_reliable_frame.test

Comment 8 errata-xmlrpc 2015-03-05 13:26:45 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-2015-0556.html