Bug 1649743

Summary: FIPS: misleading "FATAL: Module xxx not found" messages when booting
Product: Red Hat Enterprise Linux 7 Reporter: Renaud Métrich <rmetrich>
Component: dracutAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: high Docs Contact:
Priority: high    
Version: 7.6CC: dracut-maint-list, michael.dahl, mmatsuya
Target Milestone: beta   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: dracut-033-560.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 13:13:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
proposed patch none

Description Renaud Métrich 2018-11-14 12:31:25 UTC 
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
Comment 3 Masahiro Matsuya 2019-01-16 10:34:13 UTC 
I have another customer case about this bug.
I thought why sha1-mb and sha256-mb modules were not added into initramfs even if those (sha1 and sha256) are listed as fips modules. It's aliases for sha1-mb and sha256-mb modules. So, I think those aliases should be resolved into the actual module file name. I will attach a proposed patch.

Masahiro Matsuya
Comment 4 Masahiro Matsuya 2019-01-16 10:34:53 UTC 
Created attachment 1520951 [details]
proposed patch
Comment 5 Lukáš Nykrýn 2019-01-16 10:59:08 UTC 
There is already a different patch from Renaud that should fix the issue https://github.com/dracutdevs/dracut/commit/01ffcf342ae65984c655f10a2fd35019a492ee5c
devel_ack for including that to 7.7
Comment 6 Masahiro Matsuya 2019-01-17 01:38:25 UTC 
That's good to hear. Renaud++
Comment 11 errata-xmlrpc 2019-08-06 13:13:38 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, 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-2019:2289