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.

Bug 2070655

Summary:	fapolicyd does not correctly handle SIGHUP
Product:	Red Hat Enterprise Linux 9	Reporter:	Dalibor Pospíšil <dapospis>
Component:	fapolicyd	Assignee:	Radovan Sroka <rsroka>
Status:	CLOSED ERRATA	QA Contact:	Dalibor Pospíšil <dapospis>
Severity:	unspecified	Docs Contact:	Mirek Jahoda <mjahoda>
Priority:	unspecified
Version:	9.0	CC:	dapospis, jafiala, qe-baseos-security, rsroka
Target Milestone:	rc	Keywords:	AutoVerified, Triaged
Target Release:	9.1	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	fapolicyd-1.1.3-102.el9	Doc Type:	Bug Fix
Doc Text:	.`fagenrules --load` now works correctly Previously, the `fapolicyd` service did not correctly handle the signal hang up (SIGHUP). Consequently, `fapolicyd` terminated after receiving SIGHUP, and the `fagenrules --load` command did not work correctly. This update contains a fix for the problem. As a result, `fagenrules --load` now works correctly, and rule updates no longer require manual restarts of `fapolicyd`.	Story Points:	---
Clone Of:	2070639	Environment:
Last Closed:	2022-11-15 10:41:03 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:
Bug Depends On:
Bug Blocks:	2027125

Description Dalibor Pospíšil 2022-03-31 15:51:19 UTC

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

Description of problem:
fapolicyd should reload the configuration, mainly the rules on SIGHUP 

Version-Release number of selected component (if applicable):
fapolicyd-1.1-1.el9

How reproducible:
100%

Steps to Reproduce:
1. systemctl start fapolicyd
2. systemctl kill -s HUP fapolicyd
3. systemctl status fapolicyd

Actual results:
# systemctl status fapolicyd
# echo $?
3


Expected results:
# systemctl status fapolicyd
# echo $?
0

Comment 17 errata-xmlrpc 2022-11-15 10:41:03 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 (fapolicyd 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-2022:8236