Bug 2066408

Summary: REX SSH Key works for SSH but fails for REX on RHEL 8.5 Host
Product: Red Hat Satellite Reporter: Brian McCafferty <bdm>
Component: Remote ExecutionAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.9.7CC: ahumbe, aruzicka, lstejska
Target Milestone: 6.11.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-smart_proxy_remote_execution_ssh-0.5.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-05 14:34:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Brian McCafferty 2022-03-21 17:01:20 UTC
Description of problem:
REX SSH Key works for SSH but fails for REX on RHEL 8.5 Host


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

How reproducible:
For customer 100% of time, Unable to replicate in lab.


Steps to Reproduce:
1. Set RHEL 8.5 Server to DEFAULT crypto policy
2. Test SSH to Server using the REX Key ssh -vvv -i ~foreman-proxy/.ssh/id_rsa_foreman_proxy host.example.com
3. Test REX Job to same server host.example.com

Actual results:
SSH works fine from server

REX Job Fails with error - Error initializing command: Net::SSH::AuthenticationFailed - Authentication failed for user root.com

Error in Logs for RHEL 8.5 Server:
userauth_pubkey: key type ssh-rsa not in PubkeyAcceptedKeyTypes [preauth]

The error only appears when using REX Jobs, SSH Key works with direct SSH using REX Key.


Expected results:
SSH & REX Should both work

Additional info:
See Private Comments

Comment 7 Peter Ondrejka 2022-04-14 11:36:39 UTC
Verified on Satellite 6.11 sn 16, remote execution performs successfully on a rhel8.5 host

Comment 10 errata-xmlrpc 2022-07-05 14:34:49 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