Bug 1848871

Summary:	abrt fails to generate sosreport due to invalid plugin 'nfsserver'
Product:	Red Hat Enterprise Linux 7	Reporter:	Martin Kyral <mkyral>
Component:	abrt	Assignee:	ekulik
Status:	CLOSED ERRATA	QA Contact:	Martin Kyral <mkyral>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.9	CC:	ekulik, msuchy, ovasik, pvlasin
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	abrt-2.1.11-60.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-09-29 19:53:13 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 Martin Kyral 2020-06-19 06:27:47 UTC

Description of problem:
deliberately created crash of ksh was not picked up by ABRT due to failure when generating sosreport:

Jun 19 02:04:50 host-10-0-139-75 abrt-hook-ccpp: Process 27708 (ksh93) of user 0 killed by SIGSEGV - dumping core
Jun 19 02:04:52 host-10-0-139-75 abrt-server: sosreport run failed with exit code 1, log follows:
Jun 19 02:04:52 host-10-0-139-75 abrt-server: sosreport (version 3.9)
Jun 19 02:04:52 host-10-0-139-75 abrt-server: a non-existing plugin (nfsserver) was specified in the command line
Jun 19 02:04:52 host-10-0-139-75 abrt-server: a non-existing plugin (nfsserver) was specified in the command line
Jun 19 02:04:52 host-10-0-139-75 abrt-server: 'post-create' on '/var/spool/abrt/ccpp-2020-06-19-02:04:50-27708' exited with 1
Jun 19 02:04:52 host-10-0-139-75 abrt-server: Deleting problem directory '/var/spool/abrt/ccpp-2020-06-19-02:04:50-27708'

I suspect, this is caused by the recent rebase of sos to 3.9:

https://bugzilla.redhat.com/show_bug.cgi?id=1789025


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

How reproducible:


Steps to Reproduce:
1. kill ksh with pickable signal (ie 11)
2. tail -f /var/log/messages
3.

Actual results:
sosreport fails, crash dir deleted


Expected results:
crash picked up in ABRT


Additional info:
This is not the first time, ABRT gets broken by sosreport update. I wonder, if there's a way to set information flow up in order to prevent such a breakage. It would be nice of sos developers to ping their ABRT counterparts when planning to remove / split plugins so ABRT can be updated in sync. Also please note, that this kind of breakage flies under the radar of regular errata testing as it is performed on released RHEL with just ABRT updated.

Comment 12 errata-xmlrpc 2020-09-29 19:53:13 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 (abrt bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2020:3912