Bug 2129185

Summary: Checking rule updates with fagenrules is not helpful when automating changes for fapolicyd
Product: Red Hat Enterprise Linux 8 Reporter: James Marshall <jamarsha>
Component: fapolicydAssignee: Radovan Sroka <rsroka>
Status: CLOSED DUPLICATE QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.6CC: dapospis
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-10-17 08:23:02 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:

Description James Marshall 2022-09-22 20:02:28 UTC 
Description of problem:
Applying new rules with `fagenrules --load` leaves fapolicyd.service in a dead state and requires a restart of services.

The command `fagenrules --check` does not have a quiet output which is not localization friendly when making a decision regarding whether rules need to be loaded.

For stateful updates to rules for fapolicyd when installing applications, there should be a script friendly way to update rules.

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

How reproducible:
Everytime

Steps to Reproduce:
1. systemctl start fapolicyd.service
2. Add a rule to /etc/fapolicyd/rules.d/
3. Verify there is a change with: `fagenrules --check`
4. fagenrules --load
5. systemctl status fapolicyd.service

Actual results:
Service is dead

Expected results:
Either service is the same status it was prior to load or check returns script friendly results
Comment 1 Dalibor Pospíšil 2022-10-17 08:23:02 UTC 
This issue will be fixed in 8.7 release.

*** This bug has been marked as a duplicate of bug 2070639 ***