Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
If the /var/lib/setroubleshoot/email_alert_recipients file contains a list of email addresses and related filters (after_first, always, never) then the setroubleshootd process (after SELinux denials analysis) does not send the correct number of email alerts.
Version-Release number of selected component (if applicable):
setroubleshoot.x86_64 3.3.27-2.el9
How reproducible:
* always
Steps to Reproduce:
After first execution of the AVC trigger command, the following statements should be true:
* user specified by "after_first" receives 1 email
* user specified by "always" receives 0 emails
* user specified by "never" receives 1 email
After second execution of the AVC trigger command, the following statements should be true:
* user specified by "after_first" receives 1 email
* user specified by "always" receives 0 emails
* user specified by "never" receives 2 emails
Actual results:
1,0,1
2,0,2
Expected results:
1,0,1
1,0,2
Additional info:
There is a bug in the setroubleshoot code which should be fixed by this MR:
* https://gitlab.com/setroubleshoot/framework/-/merge_requests/12
I have to reformulate the assumptions to make them clear:
After first execution of the AVC trigger command, the following statements should be true:
* user specified by "after_first" received 1 email
* user specified by "always" received 0 emails
* user specified by "never" received 1 email
After second execution of the AVC trigger command, the following statements should be true:
* user specified by "after_first" did not receive any additional email (1 email in total)
* user specified by "always" received 0 emails
* user specified by "never" received 1 additional email (2 emails in total)
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 (new packages: setroubleshoot), 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-2022:2591