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.

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

Description of problem:
Fapolicyd's pretrans scriptlet implements a workaround rule and restarts the service. The communication pipe files is being recreated by the service while rpm-plugin-fapolicyd still keeps the old pipe file open at that time.


Proper solution: rpm-plugin-fapolicyd should detect the new pipe file was created and it should close the old FD and use the new file.

Viable solution: remove completely the pretrans scriptlet. The fix for the original issue was already backported to all the active z-streams so the update process should not need it anymore.

Version-Release number of selected component (if applicable):
fapolicyd-1.0.4-2.el8
fapolicyd-1.0.4-101.el9

How reproducible:
100%

Steps to Reproduce:
1. update failopicyd and other packages at the same time, e.g. rhel-8.4 -> rhel-8.6

Actual results:
yum update process gets stuck on fapolicyd live trustDB update

Expected results:
yum update proceeds smoothly

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 (Moderate: fapolicyd security, 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/RHSA-2022:1898