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.
Bug 1896875 - fapolicyd breaks system upgrade, leaving system in dead state - complete fix
Summary: fapolicyd breaks system upgrade, leaving system in dead state - complete fix
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: fapolicyd
Version: 8.3
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: 8.0
Assignee: Radovan Sroka
QA Contact: Dalibor Pospíšil
Mirek Jahoda
URL:
Whiteboard:
: 1895467 1897323 (view as bug list)
Depends On: 1895467
Blocks: 1895513 1895514 1895515 1897090 1897091 1897092
TreeView+ depends on / blocked
 
Reported: 2020-11-11 18:09 UTC by Lukas Vrabec
Modified: 2024-03-25 17:02 UTC (History)
34 users (show)

Fixed In Version: fapolicyd-1.0.2-5.el8
Doc Type: Bug Fix
Doc Text:
.`fapolicyd` no longer prevents RHEL updates When an update replaces the binary of a running application, the kernel modifies the application binary path in memory by appending the `(deleted)` suffix. Previously, the `fapolicyd` file access policy daemon treated such applications as untrusted. As a consequence, `fapolicyd` prevented these applications from opening and executing any other files. With this update, `fapolicyd` ignores the suffix in the binary path so the binary can match the trust database. As a result, `fapolicyd` enforces the rules correctly and the update process can finish.
Clone Of: 1895467
: 1897090 1897091 1897092 (view as bug list)
Environment:
Last Closed: 2021-05-18 16:22:41 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 5542661 0 None None None 2020-11-11 19:37:55 UTC
Red Hat Knowledge Base (Solution) 5573841 0 None None None 2020-11-12 20:40:35 UTC

Comment 3 Lukas Vrabec 2020-11-11 19:37:56 UTC
*** Bug 1895467 has been marked as a duplicate of this bug. ***

Comment 7 Chris Williams 2020-11-12 20:40:35 UTC
*** Bug 1897323 has been marked as a duplicate of this bug. ***

Comment 37 Amit Kumar Das 2021-04-27 06:44:30 UTC
Lukas - Thanks for confirming on RHEL-8.4 GA. Can you confirm that fix will be included in RHEL-8.3.Z rollout?

Comment 40 errata-xmlrpc 2021-05-18 16:22:41 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/RHEA-2021:1952


Note You need to log in before you can comment on or make changes to this bug.