-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
crypto-policies-20240202-1.git283706d.el9
-
None
-
None
-
1
-
rhel-sst-security-crypto
-
ssg_security
-
24
-
1
-
False
-
-
No
-
Crypto24Q1
-
- (SanityOnly) reporter confirms that the fix is working for their use-case
-
Pass
-
Not Needed
-
RegressionOnly
-
Release Note Not Required
-
None
What were you trying to do that didn't work?
Anaconda installer is trying to setup FIPS system mode by running fips-mode-setup --enable --no-bootcfg in a chroot environment which contains an ostree based filesystem.
Please provide the package NVR for which bug is seen:
crypto-policies-scripts-20231113-1.gite9247c2.el9.noarch
How reproducible:
Always
Steps to reproduce
- Create an ostree commit and serve it over http (or an ostree container)
- Use anaconda installer to deploy that commit with "ostreesetup"
this can be done by providing a kickstart file at boot time with the following content "ostreesetup --osname=rhel --url=http://host.example.com/repo --ref=rhel/9/x86_64/edge --nogpg" where the url param corresponds to the root of the ostree commit served on step 1. Make sure fips=1 inst.ks=... kernel parameters are passed at boot time. - Provide the information required by the installer, perform the installation and reboot.
- Login and check an initramfs file is present in /boot directory.
Expected results:
ostree is detected correctly and no initramfs regeneration is triggered.
Actual results
ostree is not detected correctly and a new initramfs generation is triggered.
Additional information
This seems to work in Fedora and although the ostree is not detected properly either, it makes some some additional checks that prevent the initramfs regeneration, mainly because of https://gitlab.com/redhat-crypto/fedora-crypto-policies/-/commit/a782a5578b3ef67d9bf6d8e6999807183f8e3ebc
- links to
-
RHEA-2023:120978 crypto-policies bug fix and enhancement update
- mentioned on