Bug 1461486

Summary:	setroubleshootd is not automatically stopped when sealert cannot find an alert with a specific local id
Product:	Red Hat Enterprise Linux 7	Reporter:	Milos Malik <mmalik>
Component:	setroubleshoot	Assignee:	Vit Mojzis <vmojzis>
Status:	CLOSED ERRATA	QA Contact:	Milos Malik <mmalik>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.4	CC:	lvrabec, mgrepl, mmalik, plautrba
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	setroubleshoot-3.2.30-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1394905	Environment:
Last Closed:	2018-10-30 09:47:31 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 Milos Malik 2017-06-14 14:57:16 UTC

+++ This bug was initially created as a clone of Bug #1394905 +++

Description of problem:

Version-Release number of selected component (if applicable):
setroubleshoot-server-3.2.28-3.el7.x86_64
setroubleshoot-plugins-3.0.65-1.el7.noarch

How reproducible:
* always

Steps to Reproduce:
1. get a clean RHEL-7.4 machine (targeted policy in enforcing mode)
2. generate an AVC
# passwd --help >& /root/output.txt
3. make sure the AVC is logged
# ausearch -m avc -i
4. list all alerts processed by setroubleshoot daemon
# sealert -l '*'
5. list the only alert using its Local ID, but change the Local ID slightly (for example: delete the last character or replace the last character by another character)
# sealert -l '7fd82c45-5bce-4b7d-a176-f167570ee4c2'

Actual results:
# sealert -l '7fd82c45-5bce-4b7d-a176-f167570ee4c2'
Error
query_alerts error (1003): id (7fd82c45-5bce-4b7d-a176-f167570ee4c2) not found
# ps -efZ | grep setr
system_u:system_r:setroubleshootd_t:s0-s0:c0.c1023 setroub+ 10573 1  1 10:54 ? 00:00:00 /usr/bin/python -Es /usr/sbin/setroubleshootd -f
unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 root 10581 10432  0 10:54 pts/0 00:00:00 grep --color=auto setr
# sleep 30
# ps -efZ | grep setr
system_u:system_r:setroubleshootd_t:s0-s0:c0.c1023 setroub+ 10573 1  0 10:54 ? 00:00:00 /usr/bin/python -Es /usr/sbin/setroubleshootd -f
unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 root 10584 10432  0 10:55 pts/0 00:00:00 grep --color=auto setr
# 

Expected results:
* setroubleshoot daemon terminates ASAP

Comment 1 Vit Mojzis 2018-01-19 11:51:25 UTC

https://pagure.io/setroubleshoot/c/a3720aac946552783930a58f12d332f946204e55?branch=stable

Comment 5 errata-xmlrpc 2018-10-30 09:47:31 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://access.redhat.com/errata/RHBA-2018:3100