You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 19, 2022. It is now read-only.
Kitchen upload shells out to rsync (which calls ssh). That's likely where the prompt is coming from. It's interesting that I don't tend to run into this in our own integration tests though. I may have had host key checking turned off for EC2 globally.
I'll try to dig a bit. @tmatilai might also have some thoughts.
Ah yeah, I have also configured ssh to not verify EC2 hosts. Net::SSH has that off by default. I guess we should make it configurable for knife-solo and then pass the same setting to both Net::SSH and rsync. Or at least disable the check now from rsync?
@drnic As a workaround, you should be able to make an SSH config file in your repo with something like this:
Host *.compute*.amazonaws.com # or just `*`
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
...and then pass that with --ssh-config-file/-F to knife-solo commands.
See https://travis-ci.org/drnic/bosh-inception/jobs/7058140#L179
Any thoughts on what we can do in knife-solo to auto-answer this, or have it never asked in the first place?
It seems weird - there have been ssh calls into this VM already; not sure why the "Uploading the kitchen..." stage results in this ssh check.
Ideas?
The text was updated successfully, but these errors were encountered: