Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Remote Execution engine: Error initializing command: Net::SSH::HostKeyMismatch - fingerprint 20:a9:b7:45:1a:b7:d6:42:1e:03:d1:1f:06:20:4c:e2 does not match for "172.17.0.101"
Description of problem:
Remote Execution engine remembers ssh fingerprints of clients and when client is reinstalled, it fails with:
Error initializing command: Net::SSH::HostKeyMismatch - fingerprint 20:a9:b7:45:1a:b7:d6:42:1e:03:d1:1f:06:20:4c:e2 does not match for "172.17.0.101"
Version-Release number of selected component (if applicable):
satellite-6.3.0-21.0.beta.el7sat.noarch
How reproducible:
always
Steps to Reproduce:
1. Execute remote command on client
2. Reinstall that client (or somehow force it to change sshd fingerprint)
and register it back with same name and IP
3. Attempt to execute another remote command
Actual results:
Error message mentioned above
Expected results:
I'm not saying this is a wrong behavior. It is up to somebody else, but if it is going to stay this way, that change needs to be documented.
Additional info:
Info from aruzicka:
<aruzicka> jhutar: so, apparently it is a new thing in net-ssh 4.0+ (sat 6.2 had net-ssh 2.4.something). there's an issue about this in its upstream repo, but i don't think they'll fix it anytime soon
<aruzicka> jhutar: so if you could please open a BZ and we'll probably make some fix on our side
On Sat6.5.0HTB problem is still there. Even doing a build=no and build=yes to make the provisioning in a clean for rebuilding it does not clean the ssh entry
My use case for re-kickstarting uses the following 2 commands to force a clean hosts entry for biulding (including a new kickstart token)
hammer host update --name testserver.test.com --managed yes --build no
hammer host update --name testserver.test.com --managed yes --build yes
After the second command i expect that also the entries in the ssh known_hosts files for testserver.test.com are cleaned on the sat6 serfver and all capsules.
Current behaviour is inconsistnet with e.g. the facts that are actually cleaned when switching to 'Build'
As pointed out in the upstream issue:
[ Remote Execution engine: Error initializing command: Net::SSH::HostKeyMismatch ... ]
https://projects.theforeman.org/issues/21449
My suggestion would be to set ~foreman-proxy/.ssh/config to completely ignore ssh keys by default:
Host *
UserKnownHostsFile=/dev/null
StrictHostKeyChecking=no
For RHSAT and for the Capsules.
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 (Important: Satellite 6.8 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-2020:4366