Bug 1747751
Summary: | [RFE] Ruby net-ssh doesn't support 'ed25519' ssh key type. | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Hao Chang Yu <hyu> | ||||
Component: | Remote Execution | Assignee: | Adam Ruzicka <aruzicka> | ||||
Status: | CLOSED ERRATA | QA Contact: | Peter Ondrejka <pondrejk> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 6.5.0 | CC: | ahumbe, aruzicka, bkearney, ehelms, inecas, lvrtelov, michelis.tobias, mmccune, myarboro, osousa, pcreech, pondrejk, saydas, smeyer, zhunting | ||||
Target Milestone: | 6.10.0 | Keywords: | FutureFeature, PrioBumpGSS, Triaged | ||||
Target Release: | Unused | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | tfm-rubygem-foreman_remote_execution_core-1.4.6, libsodium-1.0.17-3, tfm-rubygem-rbnacl-4.0.2-2,satellite-6.10.0-2 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2021-11-16 14:08:51 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: | |||||||
Attachments: |
|
Description
Hao Chang Yu
2019-09-01 08:13:39 UTC
Created redmine issue https://projects.theforeman.org/issues/27770 from this bug Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/27770 has been resolved. Not sure if the change got CP'd or what happened, but upstream release containing the fix just went out. Checked on Sat 6.10 sn 4, attempting to run a rex job using a ed25519 key failed with "Net::SSH::AuthenticationFailed" (task backtrace in attachment) Verification steps for reference: - cd /var/lib/foreman-proxy - ssh-keygen -o -a 100 -t ed25519 -f ssh/id_ed25519 -C "foreman-proxy@hostname" - in /etc/foreman-proxy/settings.d/remote_execution_ssh.yml set :ssh_identity_key_file: /var/lib/foreman-proxy/ssh/id_ed25519 - restart services - refresh capsule in sat ui capsule details - on host: curl https://sat_hostname:9090/ssh/pubkey >> ~/.ssh/authorized_keys - run rex job packges: tfm-rubygem-net-ssh-4.2.0-3.el7sat.noarch tfm-rubygem-foreman_remote_execution_core-1.4.2-1.el7sat.noarch (doublechecked I'm really on sn4, seems like the rex_core package version is lower than promised...) Created attachment 1791540 [details]
task-backtrace
Could you bump log level to debug in /etc/smart_proxy_dynflow_core/settings.yml and ssh_log_level in /etc/foreman-proxy/settings.d/remote_execution_ssh.yml , restart services, run the job again and attach logs from /var/log/foreman-proxy/proxy.log? Upstream bug assigned to aruzicka Still getting Net::SSH::AuthenticationFailed on Satellite 6.10 sn 9, attaching proxy.log Attempting to verify on Sat 6.10 snap 10, using steps from comment 9. The rex job remains hanging in pending state after setting the ed25519 key. Direct ssh connection from host to client via "ssh root@host -i id_ed25519" works. Nothing significant appears in the proxy log. Reproduction machine available upon ping. Checking on satellite 6.10 sn 12 with tfm-rubygem-foreman_remote_execution_core-1.4.6-1.el7sat.noarch, unfortunately I'm still getting to the infinite pending state when running rex job with ed25519 key Checked on Satellite 6.10 sn 24, the packages are present now and rex performs successfully with ed25519 key (steps from #comment 9). Unfortunately, there is a problem with global registration that does not honor the key setting in /etc/foreman-proxy/settings.d/remote_execution_ssh.yml when setting up remote execution. It always pulls id_rsa_foreman_proxy, so the user needs to do curl https://sat_hostname:9090/ssh/pubkey >> ~/.ssh/authorized_keys manually to set up ed25519 rex. That's odd, it seems to work well on a fresh machine I just deployed. #33 was due to omitted feature refresh on capsule, moving to verified 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.10 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-2021:4702 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |