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 2070036 - fapolicyd service causes dracut to generate broken initrd
Summary: fapolicyd service causes dracut to generate broken initrd
Keywords:
Status: CLOSED DUPLICATE of bug 2066300
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: fapolicyd
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Radovan Sroka
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 2015802 2070579
TreeView+ depends on / blocked
 
Reported: 2022-03-30 10:49 UTC by Ales Musil
Modified: 2022-11-30 08:58 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2070579 (view as bug list)
Environment:
Last Closed: 2022-04-01 12:14:10 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)
Dracut output - failing host (31.49 KB, text/plain)
2022-03-30 10:49 UTC, Ales Musil
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-117249 0 None None None 2022-03-30 10:53:00 UTC
Red Hat Issue Tracker SECENGSP-4475 0 None None None 2022-03-30 16:52:40 UTC

Description Ales Musil 2022-03-30 10:49:11 UTC
Created attachment 1869337 [details]
Dracut output - failing host

Created attachment 1869337 [details]
Dracut output - failing host

Description of problem:
Any new initrd image that is generated, once fapolicyd service is started,
makes the machine unbootable. The kernel panics that it cannot execute init.

Version-Release number of selected component (if applicable):
kernel-4.18.0-372.3.1.el8.x86_64
fapolicyd-1.1-1.el8.x86_64
dracut-049-201.git20220131.el8.x86_64
dracut-squash-049-201.git20220131.el8.x86_64
dracut-network-049-201.git20220131.el8.x86_64
dracut-config-generic-049-201.git20220131.el8.x86_64
dracut-config-rescue-049-201.git20220131.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1. yum install fapolicyd -y
2. service fapolicyd start
3. Run dracut -fv /boot/initramfs-$(uname -r).img
4. Reboot

Actual results:
The host ends up with kernel not being able to execute init.

Additional info:
Clean host without the fapolicyd does not have this problem.

Comment 1 Ales Musil 2022-03-30 10:49:40 UTC
Created attachment 1869338 [details]
Dracut - clean host

Comment 6 Ales Musil 2022-03-31 05:18:52 UTC
Thank you for the investigation, I did not connect the dots yesterday but it is probably connected to BZ#2066300 maybe even the same problem.

Comment 10 Radovan Sroka 2022-04-01 12:14:10 UTC

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


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