Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1823840

Summary: abrt-cli list reports restraintd killed by SIGTRAP
Product: [Retired] Restraint Reporter: Marco Patalano <mpatalan>
Component: generalAssignee: Carol Bouchard <cbouchar>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.2.0CC: asavkov, bpeck, breilly, cbeer, cbouchar, danrodri, jbastian
Target Milestone: 0.2.1   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-23 11:44:29 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 Marco Patalano 2020-04-14 15:27:37 UTC 
Description of problem: At the end of my some of my automation for NVMe-FC and HW RAID, we run a log_checker script which was designed to find issues observed during the test run. Within the past few days, the script has been reporting a failure when checking for errors in abrt:

INFO: [2020-04-14 10:59:28] Running: 'abrt-cli list'...
id 0b0cef36a9d0b4a8ce1524051d84641d76d28909
reason:         restraintd killed by SIGTRAP
time:           Tue 14 Apr 2020 10:27:57 AM EDT
cmdline:        /usr/bin/restraintd
uid:            0
Directory:      /var/spool/abrt/ccpp-2020-04-14-10:27:57-2196
Reported:       cannot be reported

Below is an example job:
https://beaker.engineering.redhat.com/jobs/4194739


Version-Release number of selected component (if applicable):
restraint-0.2.0-1.el7bkr

How reproducible: Often


Steps to Reproduce:
1. reproduced during NVMe-FC automation in beaker


Actual results: abrt error observed


Expected results: no abrt errors


Additional info:
Comment 1 Marco Patalano 2020-04-15 12:57:50 UTC 
FYI, I reran a job that previously encountered these abrt errors, but used an older version of restraint "harness='restraint-rhts-0.1.45
beakerlib-redhat'". I no longer saw the errors reported previously. 

https://beaker.engineering.redhat.com/jobs/4197370

Marco
Comment 2 Marco Patalano 2020-04-16 19:14:30 UTC 
I just re-ran the job with an added task to download the abrt core dump. It can be found here:

http://kdump.usersys.redhat.com/vmcore/storageqe/kdump_cores/storageqe-28.sqe.lab.eng.bos.redhat.com/abrt/2020-04-16-15-08-54/
Comment 3 Daniel Rodríguez 2020-05-23 11:44:29 UTC 
Root cause here was the calls to "g_error ()" for logging introduced in 0.2.0. They were removed in 0.2.1 release.