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.
Bug 2274453 - With FIPS enabled on RHEL9, satellite-installer failed on starting Foreman Proxy
Summary: With FIPS enabled on RHEL9, satellite-installer failed on starting Foreman Proxy
Keywords:
Status: CLOSED DUPLICATE of bug 2274258
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.16.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-04-11 06:58 UTC by matt jia
Modified: 2024-04-11 09:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-04-11 09:09:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-24532 0 None None None 2024-04-11 07:04:12 UTC

Description matt jia 2024-04-11 06:58:21 UTC 
Description of problem:

A fresh Satellite 6.16 installation on RHEL9 with FIPS enabled failed with:

~~~
2024-04-11 02:17:42 [ERROR ] [configure] Apr 11 02:17:41 sat616-rhel9.xxx.xxx.xx.xx.com systemd[1]: Starting Foreman Proxy...
2024-04-11 02:17:42 [ERROR ] [configure] Apr 11 02:17:42 sat616-rhel9.xxx.xx.xx.xx.xx smart-proxy[27075]: Errors detected on startup, see log for details. Exiting: Could not parse PKey
2024-04-11 02:17:42 [ERROR ] [configure] Apr 11 02:17:42 sat616-rhel9.x.x.x.x.x systemd[1]: foreman-proxy.service: Main process exited, code=exited, status=1/FAILURE
2024-04-11 02:17:42 [ERROR ] [configure] Apr 11 02:17:42 sat616-rhel9.x.x.x.x.x systemd[1]: foreman-proxy.service: Failed with result 'exit-code'.
2024-04-11 02:17:42 [ERROR ] [configure] Apr 11 02:17:42 sat616-rhel9.x.x.x.x.com systemd[1]: Failed to start Foreman Proxy.
~~~

Checking the foreman-proxy log, it has:

~~~
2024-04-11T02:17:42  [E] Unable to load private SSL key. Are the values correct in settings.yml and do permissions allow reading?
2024-04-11T02:17:42  [W] Error details for Unable to load private SSL key. Are the values correct in settings.yml and do permissions allow reading?: <OpenSSL::PKey::PKeyError>: Could not parse PKey
/usr/share/foreman-proxy/lib/launcher.rb:106:in `read'
/usr/share/foreman-proxy/lib/launcher.rb:106:in `load_ssl_private_key'
/usr/share/foreman-proxy/lib/launcher.rb:96:in `https_app'
/usr/share/foreman-proxy/lib/launcher.rb:132:in `launch'
/usr/share/foreman-proxy/bin/smart-proxy:6:in `<main>'
2024-04-11T02:17:42  [E] Error during startup, terminating
2024-04-11T02:17:42  [W] Error details for Error during startup, terminating: <OpenSSL::PKey::PKeyError>: Could not parse PKey
~~~

The private key seems alright:

~~~
ls -lrt /etc/foreman-proxy
total 52
-rw-r--r--. 1 root root             0 Apr  3 12:57 migration_state
-r--r-----. 1 root foreman-proxy 2529 Apr 11 02:08 ssl_ca.pem
-r--r-----. 1 root foreman-proxy 2529 Apr 11 02:08 foreman_ssl_ca.pem
-rw-r-----. 1 root foreman-proxy  771 Apr 11 02:08 ansible.env
-rw-r-----. 1 root foreman-proxy 3438 Apr 11 02:08 settings.yml
-r--r-----. 1 root foreman-proxy 3272 Apr 11 02:08 ssl_key.pem
-r--r--r--. 1 root foreman-proxy 8477 Apr 11 02:08 ssl_cert.pem
-r--r-----. 1 root foreman-proxy 3272 Apr 11 02:08 foreman_ssl_key.pem
-r--r--r--. 1 root foreman-proxy 8483 Apr 11 02:08 foreman_ssl_cert.pem
drwxr-xr-x. 2 root root          4096 Apr 11 02:17 settings.d
~~~

Version-Release number of selected component (if applicable):

6.16

How reproducible:

Easy

Steps to Reproduce:

Install Satellite 6.16 on RHEL9 with FIPS enabled

Actual results:

The installer failed


Expected results:

the installer should complete successfully.



Additional info:
Comment 3 Ron Lavi 2024-04-11 09:09:09 UTC 

*** This bug has been marked as a duplicate of bug 2274258 ***
Note You need to log in before you can comment on or make changes to this bug.