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:
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

This issue will be fixed in 8.7 release.

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