-
Notifications
You must be signed in to change notification settings - Fork 23.8k
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
Error reading SSH protocol banner timeout when using network_cli connection #69267
Comments
Files identified in the description: If these files are incorrect, please update the |
The issue should be fixed by PR #68184 needs_info |
@ganeshrn we've tried to modify the banner timeout, but still have the same issue. The timeout only delay the error from 15s to 30s. The problem is the bastion server doesn't seem to start the proxycommand at all. We did tcpdump and see the connection from client to bastion server can be established. However right after the handshake the connection is closed by a FIN from client. When test directly using ssh command from the client it works as expected so the network connectivity is fine. Only when running from ansible-playbook we have this issue |
|
@dragon0087
Try increasing the connect_timeout Refer: https://docs.ansible.com/ansible/devel/network/user_guide/network_debug_troubleshooting.html#persistent-connection-idle-timeout Even after that if you are seeing the issue enable the persistent device logging to identify which command is failing (gerp for |
@ganeshrn change persistent timeout didn't help. persistent logging give only one more line that pretty much saying the same thing The issue is tcp connection can be established to bastion server but close immediately after GEX. |
btw this is our ansible.cfg
|
@dragon0087 In your ansible.cfg file I can't see any values for connect_timeout. Is it set somewhere else?
|
@ganeshrn yes, I tried that by export env variable. |
+1 |
@seansabour This issue is waiting for your response. Please respond or the issue will be closed. |
Hi @ganeshrn - can you remove the needs_info label, i don't want this issue to be closed ^ |
@seansabour The |
@ganeshrn Cool, thanks for the heads up! I've opened the issue in the new repo |
Closing per above. |
SUMMARY
When using the network_cli we are seeing issues with ssh protocol banner timeout coming from paramiko. When running the SSH proxy command manually from the server it has no problems connecting.
ISSUE TYPE
COMPONENT NAME
network_cli connection plugin
ANSIBLE VERSION
I've also tested this with ansible2.8.4 with python2.7.5 and same issue occurs
CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE
EXPECTED RESULTS
To be able to successfully connect to the box and pull facts
ACTUAL RESULTS
SSH protocol banner timeout
The text was updated successfully, but these errors were encountered: