-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Improvement-11380][scp-host.sh] Set StrictHostKeyChecking=no option to ssh #11382
Conversation
Hi @rickchengx , to target specific issue from PR, we recommend use keyword fix: #issue_id or close: #issue_id or closes: #issue_id in your PR describe(not title, just desc). It would not only connect issue to PR but also close issue automatically when PR is be closed. |
Sure. Thanks for your advice, I've added the keyword close: #issue_id. |
Kudos, SonarCloud Quality Gate passed! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks.
…to ssh (apache#11382) * [Improvement][scp-host.sh] Set StrictHostKeyChecking=no option to ssh * add StrictHostKeyChecking=no option to status-all.sh
…to ssh (apache#11382) * [Improvement][scp-host.sh] Set StrictHostKeyChecking=no option to ssh * add StrictHostKeyChecking=no option to status-all.sh
Purpose of the pull request
This PR close: #11380
Even if the password-free account is configured, when the user uses the scp-host.sh script to log in to the machine for the first time, an error (Host key verification failed.) may occur.
So set the
-o StrictHostKeyChecking=no
option to ssh inscp-hosts.sh
.Brief change log
Verify this pull request
This pull request is code cleanup without any test coverage.