Bug 2070639

Summary:	fapolicyd does not correctly handle SIGHUP
Product:	Red Hat Enterprise Linux 8	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:	8.6	CC:	jamarsha
Target Milestone:	rc	Keywords:	AutoVerified, Triaged
Target Release:	8.7
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	fapolicyd-1.1.3-8.el8	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 the SIGHUP signal, and the `fagenrules --load` command did not work properly. 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:
Clones:	2070655 (view as bug list)		Environment:
Last Closed:	2022-11-08 09:51:54 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:	2026666

Description Dalibor Pospíšil 2022-03-31 15:47:34 UTC

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

Version-Release number of selected component (if applicable):
fapolicyd-1.0.2-6.el8

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 Dalibor Pospíšil 2022-10-17 08:23:02 UTC

*** Bug 2129185 has been marked as a duplicate of this bug. ***

Comment 19 errata-xmlrpc 2022-11-08 09:51:54 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:7627