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:

Satellite installation on fips enabled rhel 7.6 fails with:

[ INFO]  /Stage[main]/Certs::Ca/Ca[katello-server-ca]: Scheduling refresh of Certs_bootstrap_rpm[katello-ca-consumer-hostname.example.com]
[ERROR]  /Stage[main]/Certs::Ca/Privkey[/etc/pki/katello/private/katello-default-ca.key]: Could not evaluate: Execution of '/usr/bin/openssl rsa -in /root/ssl-build/katello-default-ca.key -out /root/ssl-build/katello-default-ca.key.tmp -passin file:/etc/pki/katello/private/katello-default-ca.pwd' returned 1: unable to load Private Key
[ERROR] 139738391898000:error:060800A3:digital envelope routines:EVP_DigestInit_ex:disabled for fips:digest.c:256:

... (will attach log excrept)

Version-Release number of selected component (if applicable):
Satellite 6.5 snap 4, satellite-6.5.0-4.beta.el7sat.noarch

How reproducible:
always 

Additional info:
Does not occur on non-fips, does not occur during upgrade from previous snap

How to reproduce:
- install satellite on a non-fips rhel machine
- enable fips mode on the rhel
- try to rename via satellite-change-hostname

The installer triggered by s-c-h fails as mentioned above at 
/usr/bin/openssl rsa -in /root/ssl-build/katello-default-ca.key -out /root/ssl-build/katello-default-ca.key.tmp -passin file:/etc/pki/katello/private/katello-default-ca.pwd' returned 1: unable to load Private Key

This does happen when satellite installed in a non-fips mode is being renamed in a fips mode. 

Perhaps the katello-default-ca.key from non-fips install is not good enough for fips, so if the installer could create the key valid for both cases, we would be good.

We are not planning to support upgrade to FIPS, so I am closing this out.