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.
Description of problem:
If I call 'fips-mode-setup --enable' in my test, the current crypto policy - DEFAULT - is chosen instead of FIPS.
Test link http://artifacts.osci.redhat.com/baseos-ci/brew-build/47/89/88/47898875/https___baseos-jenkins.rhev-ci-vms.eng.rdu2.redhat.com-ci-artemis/33430/tmpM7PD3f.01/recipes/1/tasks/7/logs/taskout.log
:: [ 13:59:48 ] :: [ BEGIN ] :: Running 'fips-mode-setup --check'
Installation of FIPS modules is not completed.
FIPS mode is disabled.
:: [ 13:59:48 ] :: [ PASS ] :: Command 'fips-mode-setup --check' (Expected 0, got 0)
:: [ 13:59:48 ] :: [ BEGIN ] :: Start FIPS mode :: actually running 'fips-mode-setup --enable'
Kernel initramdisks are being regenerated. This might take some time.
Setting system policy to FIPS
Note: System-wide crypto policies are applied on application start-up.
It is recommended to restart the system for the change of policies
to fully take place.
FIPS mode will be enabled.
Please reboot the system for the setting to take effect.
...reboot...
:: [ 14:01:17 ] :: [ BEGIN ] :: FIPS mode is enabled :: actually running 'fips-mode-setup --is-enabled'
:: [ 14:01:18 ] :: [ FAIL ] :: FIPS mode is enabled (Expected 0, got 1)
:: [ 14:01:18 ] :: [ BEGIN ] :: Running 'fips-mode-setup --check'
FIPS mode is disabled.
Inconsistent state detected.
:: [ 14:01:19 ] :: [ FAIL ] :: Command 'fips-mode-setup --check' (Expected 0, got 1)
If I connect to the machine and try it manually:
# fips-mode-setup --enable
Setting system policy to FIPS
Note: System-wide crypto policies are applied on application start-up.
It is recommended to restart the system for the change of policies
to fully take place.
FIPS mode will be enabled.
Please reboot the system for the setting to take effect.
# reboot
After reboot:
# fips-mode-setup --check
FIPS mode is disabled.
Inconsistent state detected.
Version-Release number of selected component (if applicable):
crypto-policies-20220815-1.git0fbe86f.el9.noarch
How reproducible:
always
Steps to Reproduce:
1. fips-mode-setup --enable
2. reboot
3. fips-mode-setup --check
Actual results:
Disabled FIPS after reboot
Expected results:
Enabled FIPS after reboot