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:

REX job failed when you enable FIPS on RHEL 8 hosts

Version-Release number of selected component (if applicable):
satellite-6.7.0-5.beta.el7sat.noarch

How reproducible:
New installation of 6.7 Beta 

Steps to Reproduce:

1. Register a client to your satellite server 

2. Check that does your connected system has applicable errata to apply.

2. Enable FIPS on your RHEL 8 system. 

3. Attempt to execute the remote command


Actual results:

Error initializing command: Net::SSH::HostKeyMismatch - fingerprint (could not generate fingerprint: Digest initialization failed: disabled for fips) does not match for "client.example.com,1.7.1.5"

Exit status: EXCEPTION


Expected results:

The remote command should work even if you have FIPS enabled host


Additional info:

A customer has reported that a workaround is to change the job category of REX jobs from "Commands" to "Ansible Commands." I have just confirmed that a REX job executed by Satellite 6.7 on a FIPS-enabled RHEL 8 content host fails using the Commands job category, but the same job succeeds when the job category is changed to Ansible Commands.

Verified on Satellite 7 snap 4, ssh type rex job is executed successfully against FIPS enabled RHEL8 host

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.11 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.

https://access.redhat.com/errata/RHSA-2022:5498