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
[BUG] salt-ssh hanging due to non-exposed host key acceptance prompt #62782
Comments
You should be able to workaround this in the roster config. ssh_options:
- StrictHostKeyChecking=accept-new If the host key has changed, you'll either need to manually update it, or (NOT RECOMMENDED) disable checking completely. |
Right; I know how to work around it, but this is unexpected behavior and a regression; see e.g. the description for
(Emphasis added) |
…stack#62782 The shell.KEY_VALID_RE regex only matches messages containing '(yes/no)', and not messages containing '(yes/no/[fingerprint])' This leads to the salt-ssh command hanging, (Shell._run_cmd waits for data on stdout) while the ssh command is waiting on input. Fix by updating the KEY_VALID_RE regex to match both prompts
Description
When performing
salt-ssh
, the command seems to hang indefinitely.This is due to the ssh prompt to accept the (ssh-)minion's host key not being floated to an interactive prompt on the shell; it seems to never even escape from
TRACE
log level.Setup
N/A
Steps to Reproduce the behavior
(See attached)
salt-ssh.trace.log
Expected behavior
The "The authenticity of host ... can't be established. ..." prompt is displayed during salt-ssh call and can be answered in an interactive shell.
(This does not happen. No output is displayed, and even explicitly entering 'yes\n' in the console after the prompt is passed to the trace, it has no effect.)
Screenshots
N/A
Versions Report
salt --versions-report
Additional context
The target "ssh minion" is running the same OS and release, though I doubt it matters since SSH never fully establishes.
The text was updated successfully, but these errors were encountered: