Bug 1997608

Summary:	Remote execution fails with fingerprint does not match error
Product:	Red Hat Satellite	Reporter:	nikhjain <nikhjain>
Component:	Ansible	Assignee:	nalfassi
Status:	CLOSED NOTABUG	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.9.0	CC:	aruzicka, lstejska, nalfassi, saydas
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused	Flags:	nalfassi: needinfo? (nikhjain)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-08 08:46:01 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 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.