Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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:
Having a FIPS enabled satellite 6.5 server, attempting to install external capsule on a FIPS enabled rhel 7 server.
Installaition failses in step "Resetting puppet server version param..."
with "Systemd start for httpd failed!" (logs in attachment)
Version-Release number of selected component (if applicable):
Satellite 6.5 snap 16
How reproducible:
always
Steps to Reproduce:
1. install capsule packages on fips machine (in my case from dogfood server)
2. on satellite run capsule-certs-gernerate, copy certs to capsule
3. on capsule run satellite-installer --scenario capsule... (capsule-certs-gernerate)
Actual results:
httpd fails to start
Expected results:
capsule installed as expected
Additional info:
Info from more investigation, when looking at /etc/pki/katello/private/$(hostname)-foreman-proxy-client-bundle.pem,
on FIPS-enabled system, it has a form of pkcs1:
-----BEGIN RSA PRIVATE KEY-----
...
-----END RSA PRIVATE KEY-----
While on non-FIPS system, it is pkcs8:
-----BEGIN PRIVATE KEY-----
...
-----END PRIVATE KEY-----
As https://bugzilla.redhat.com/show_bug.cgi?id=1025057 mentions, it seems like a limitation of mod_ssl to support pkcs8
keys. I was not able to convert pkcs8 to pkcs1 on FIPS-enable machine, probably because of some algorithm being used there (perhaps MD5)
The best solution I can think of is removing the SSLProxyMachineCertificateFile option, as it doesn't look like it has any reason to be there
from functionality point of view (waiting for confirmation)
It seems like this workaround https://github.com/theforeman/puppet-certs/pull/243 works on FIPS machine, while keeping the setting for proxy client cert. Deployed it on the reproducer machine for more testing. The installer passed fine with that one.
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/RHSA-2019:1222