Description of problem:
Run global registration curl command on FIPS-enabled RHEL8 host. The process fails on katello-ca-consumer installation step with:
Running transaction test
Error: Transaction test error:
package katello-ca-consumer-hostname.redhat.com-1.0-1.noarch does not verify: no digest
This has been described before for RHEL8 FIPS, see https://access.redhat.com/solutions/4460971
The suggested workaround from the kcs is using "rpm -ivh --nodigest --nofiledigest" but I'm not sure if we even want to handle the issue within the template.
Version-Release number of selected component (if applicable):
Satellite 6.9 snap 11
To be establised. Probably some logic in the template to trigger a workaround or at least a user warning and link to the kcs. Alternatively, we could find a way to rebuild katello-ca-consumer to avoid digest-check.
Non-FIPS RHEL8 works as expected
I think for 6.9 we should extend the KCS with the note about the registration and the fact it fails with this error. We can also add instructions how to modify the template. That would be
1) clone the Global Registration template, call it e.g. Global Registration FIPS
2) change the line "yum localinstall $CONSUMER_RPM -y" to "rpm -ivh --nodigest --nofiledigest $CONSUMER_RPM" (please test before publish, I don't have the env at hand)
3) start using this template by selecting it at Settings -> Provisioning -> Default Global registration template, select the "Global Registration FIPS"
The global template can't be tweaked per OS. We could easily detect this by checking
> sysctl crypto.fips_enabled
if it returns 1, it means it's enabled and we should use the rpm command, otherwise we can use yum.
Created redmine issue https://projects.theforeman.org/issues/31992 from this bug
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31992 has been resolved.
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 (Moderate: Satellite 6.10 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.