Bug 2070655

Summary: fapolicyd does not correctly handle SIGHUP
Product: Red Hat Enterprise Linux 9 Reporter: Dalibor Pospíšil <dapospis>
Component: fapolicydAssignee: Radovan Sroka <rsroka>
Status: CLOSED ERRATA QA Contact: Dalibor Pospíšil <dapospis>
Severity: unspecified Docs Contact: Mirek Jahoda <mjahoda>
Priority: unspecified    
Version: 9.0CC: dapospis, jafiala, qe-baseos-security, rsroka
Target Milestone: rcKeywords: AutoVerified, Triaged
Target Release: 9.1   
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