RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1461486 - setroubleshootd is not automatically stopped when sealert cannot find an alert with a specific local id
Summary: setroubleshootd is not automatically stopped when sealert cannot find an aler...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: setroubleshoot
Version: 7.4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Vit Mojzis
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-14 14:57 UTC by Milos Malik
Modified: 2018-10-30 09:47 UTC (History)
4 users (show)

Fixed In Version: setroubleshoot-3.2.30-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1394905
Environment:
Last Closed: 2018-10-30 09:47:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3100 0 None None None 2018-10-30 09:47:58 UTC

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 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


Note You need to log in before you can comment on or make changes to this bug.