Bug 1997608 - Remote execution fails with fingerprint does not match error [NEEDINFO]
Summary: Remote execution fails with fingerprint does not match error
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: nalfassi
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-25 14:05 UTC by nikhjain
Modified: 2023-08-09 09:11 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-08 08:46:01 UTC
Target Upstream Version:
Embargoed:
nalfassi: needinfo? (nikhjain)

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36446 0 Normal New Remote execution fails with fingerprint does not match error 2023-07-21 08:45:41 UTC
Red Hat Issue Tracker SAT-18035 0 None None None 2023-06-01 15:11:29 UTC
Red Hat Knowledge Base (Solution) 3708891 0 None None None 2021-08-26 08:12:30 UTC

Description nikhjain 2021-08-25 14:05:07 UTC 
Description of problem:
Remote Execution remembers ssh fingerprints of client system and it fails with: 

Error initializing command: Net::SSH::HostKeyMismatch - fingerprint <fingerprint> does not match


Version-Release number of selected component (if applicable):
satellite-6.8.6-1.el7sat.noarch

How reproducible:
Always


Steps to Reproduce:
1. Perform remote execution job on client system.
2. Somehow change sshd fingerprint on client system.
3. Perform remote execution job on client system again.

Actual results:
Error initializing command: Net::SSH::HostKeyMismatch - fingerprint <fingerprint> does not match


Expected results:
Remote execution job should work properly without re-registering client system to satellite server.
Comment 12 nalfassi 2023-05-29 09:27:41 UTC 
Created redmine issue https://projects.theforeman.org/issues/36446 from this bug
Comment 17 nalfassi 2023-08-08 08:46:01 UTC 
We were unable to reproduce the issue on the latest version of Satellite (tried on both 6.11 and 6.13 versions).
As a result, I am closing the BZ ticket. However, please note that if the issue reoccurs or if additional information becomes available, we can reopen the ticket for further investigation.
Note You need to log in before you can comment on or make changes to this bug.