Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Reproduces also on RHEL 8
This bug was initially created as a copy of Bug #1649743
I am copying this bug because:
Description of problem:
When booting a RHEL7.6 system with FIPS, the journal records the following messages:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
# journalctl -b | grep FATAL
dracut-pre-trigger[241]: modprobe: FATAL: Module sha1 not found.
dracut-pre-trigger[241]: modprobe: FATAL: Module sha256 not found.
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
These are due to the initramfs not containing the sha1 and sha256 modules because they are blacklisted in /lib/modprobe.d/dist-blacklist.conf:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
# crypto algorithms
blacklist sha1-mb
# see bz #1562114
blacklist sha256-mb
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
This causes dracut's instmods to just ignore these.
Because the kernel provides a generic algo for these, there is no need to output these misleading and confusing messages.
Version-Release number of selected component (if applicable):
dracut-fips-033-554.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Boot with fips enabled
2. Check the journal
Actual results:
# journalctl -b | grep FATAL
Nov 14 13:14:05 vm-fips7 dracut-pre-trigger[241]: modprobe: FATAL: Module sha1 not found.
Nov 14 13:14:05 vm-fips7 dracut-pre-trigger[241]: modprobe: FATAL: Module sha256 not found.
Expected results:
No message
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 (dracut 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/RHBA-2022:2105