-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
Ansible SSH problems delegate_to and closing control socket #30760
Comments
Are you specifying the remote user somewhere? needs_info |
@s-hertel Same user remotely as I use locally using SSH keys to log in and sudo for any jobs. |
I'm seeing very similar behaviour, not using delegate_to, but become_user. This is breaking the ssh pipelining, and thus requiring world readable tmpfiles in 2.4. SSH debug output indicates the same problem, read_header failed and falls back to a non-pipelined connection 2.3 works perfectly. |
@denefoster We also use become with these tasks, but not become_user at least. I need to do some more digging. But I have some other 2.4 problems to investigate as well. |
I'm also running into an issue here. It seems related. Pipelining seems to be broken for me in 2.4. example:
Result when running playbook using that task:
I have enabled it in my ansible.cfg and it was running fine in 2.3.2 as shown below. In 2.4. the basic command requires the use of tmp files again.
|
+1 having the same problem of @StephanZaat myself |
Ansible cannot seem to handle omitting delegate_to since v2.4.0.0. Possibly related: ansible/ansible#30760
) Ansible cannot seem to handle omitting delegate_to since v2.4.0.0. Possibly related: ansible/ansible#30760
Can you please test with a newer version of Ansible to see if this is still an issue? needs_info |
@ashemedai This issue is waiting for your response. Please respond or the issue will be closed. |
I can no longer test this scenario. While I am still using Ansible, it is in a completely different set up. |
ISSUE TYPE
Bug Report
COMPONENT NAME
ssh
ANSIBLE VERSION
CONFIGURATION
% ansible-config dump --only-changed
CACHE_PLUGIN(ansible.cfg) = memory
COMMAND_WARNINGS(ansible.cfg) = True
DEFAULT_BECOME_ASK_PASS(ansible.cfg) = True
DEFAULT_BECOME_METHOD(ansible.cfg) = sudo
DEFAULT_GATHERING(ansible.cfg) = smart
DEFAULT_MANAGED_STR(ansible.cfg) = This file is managed by Ansible, don't make changes here - they will be overwritten.
DEFAULT_ROLES_PATH(ansible.cfg) = ['roles']
DEFAULT_UNDEFINED_VAR_BEHAVIOR(ansible.cfg) = True
DEFAULT_VAULT_PASSWORD_FILE(ansible.cfg) = bin/vault_passwords.sh
DEPRECATION_WARNINGS(ansible.cfg) = True
RETRY_FILES_ENABLED(ansible.cfg) = False
RETRY_FILES_SAVE_PATH(ansible.cfg) = /tmp
SYSTEM_WARNINGS(ansible.cfg) = True
OS / ENVIRONMENT
Debian GNU/Linux 8.9 (jessie)
SUMMARY
A playbook with a delegate_to another host seems to cause full or intermittent SSH socket closures.
STEPS TO REPRODUCE
We have a playbook and role for registering hosts on our Nagios monitoring system. This involves a delegate_to the Nagios monitoring server.
This is with no ssh_connection section or active .ssh/config.
EXPECTED RESULTS
As with 2.3.x.0 that all systems are registered on the Nagios server without problems.
ACTUAL RESULTS
And from this point on the hosts never really recover.
If I use a playbook without any delegate_to I don't have these issues. It could very well be another cause, but the
delegate_to
is the only clear lead I have so far.The text was updated successfully, but these errors were encountered: