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 1910433 - REX is not possible on RHEL 8 when FUTURE crypto policy is set from Satellite 6.8
Summary: REX is not possible on RHEL 8 when FUTURE crypto policy is set from Satellite...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.8.0
Hardware: All
OS: All
unspecified
high
Target Milestone: 6.11.0
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-23 21:51 UTC by Sayan Das
Modified: 2022-07-05 14:28 UTC (History)
3 users (show)

Fixed In Version: tfm-rubygem-smart_proxy_remote_execution_ssh-0.5.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-05 14:28:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:5498 0 None None None 2022-07-05 14:28:45 UTC

Description Sayan Das 2020-12-23 21:51:06 UTC 
Description of problem:

Can't perform REX from Satellite 6.8 UI on RHEL 8.2 when FUTURE crypto policy is set.

But ssh as foreman-proxy user, from CLI, works just fine.


Version-Release number of selected component (if applicable):
Satellite 6.8
RHEL 8.2 [ Hopefully 8.3 as well ]
Crypto Policy: FUTURE  [ FIPS as well ]

How reproducible:
Always


Steps to Reproduce:
1. Ensure Satellite 6.8 is configured as per https://access.redhat.com/solutions/5393241 

2. Register a RHEL 8.2 host with Satellite and the RHEL 8.2 host must have the crypto-policy set as FUTURE.

3. Copy the foreman-proxy ssh keys to the RHEL 8 host and test ssh connectivity from command line.

4. Initiate a simple "uptime" command-based REX job from satellite UI for the same host.

Actual results:

3 is successful but at 4 i.e. REX from UI, the job will fail with the following error.
~~
Error initializing command: Net::SSH::AuthenticationFailed - Authentication failed for user root.com
~~


Expected results:


3 and 4 both should succeed.


Additional info:

As soon as we set back the crypto policy to LEGACY or DEFAULT, REX will work just fine.
Comment 8 Peter Ondrejka 2022-01-14 14:37:03 UTC 
Verified on Satellite 7.0 snap 4, both ansible and ssh type rex job ran successfully against RHEL8 host with FUTURE crypto policy enabled
Comment 11 errata-xmlrpc 2022-07-05 14:28:38 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.