Your message dated Wed, 6 Sep 2017 02:38:07 +0200 with message-id <[email protected]> and subject line ansible/SSH connections sometimes hang when PUTing the module (ping) has caused the Debian Bug report #778825, regarding ansible/SSH connections sometimes hang when PUTing the module (ping) to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 778825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778825 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: ansible Version: 1.7.2+dfsg-2 Severity: important Tags: ipv6 Dear Maintainer, * What led up to the situation? I wanted to get my hands on ansible and started their introduction, put two test hosts into /etc/ansible/hosts and tested 'ansible all -m ping'... :o) * What exactly did you do (or not do) that was effective (or ineffective)? aptitude install ansible vim /etc/ansible/hosts ansible all -m ping Afterwards I checked with the current upstream release from github: git clone ... git checkout release1.8.4 source hacking/env ansible all -m ping # (same issue) Asked for help in the ansible IRC channel and was redirected to the github issue tracker. Opened up an issue with the github tracker, which got rejected/closed with "go ask your user questions somewhere else". So, I found another time slot for this issue and tried IPv4 vs. IPv6 by setting the IP addresses via ansible_ssh_host in the inventory. Seems like there is an issue with the persistent SSH ControlMaster stuff on IPv6... Behaviour is the same for jessies ansible-1.7.2 and upstream ansible-1.8.4. Maybe this is actually related to the OpenSSH release shipped with jessie? Unfortunately, I could not find a way to enable debug logging of the SSH client for ansible SSH connections. * What was the outcome of this action? Sometimes all ansible pings passed, sometimes on of the hosts did hang, sometimes the other one and sometimes even both when SSHing over IPv6. When manually setting ansible_ssh_host to the IPv4 address of the host, I could ot reproduce the issue. * What outcome did you expect instead? All hosts passing the ansible ping all the time on the current version of the Internet Protocol. :o) -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ansible depends on: ii python 2.7.8-3 ii python-crypto 2.6.1-5+b2 ii python-httplib2 0.9+dfsg-2 ii python-jinja2 2.7.3-1 ii python-paramiko 1.15.1-1 ii python-pkg-resources 5.5.1-1 ii python-yaml 3.11-2 Versions of packages ansible recommends: ii python-selinux 2.3-2 Versions of packages ansible suggests: ii ansible-doc 1.7.2+dfsg-2 pn sshpass <none> -- Configuration Files: /etc/ansible/hosts changed: [htzcluster] argon.hc.vangeuns.net ansible_ssh_user=root neon.hc.vangeuns.net ansible_ssh_user=root -- no debconf information
--- End Message ---
--- Begin Message ---Hi Linus, since we haven't heard any feedback in a year and I can't reproduce the issue, I'm closing this bug. Feel free to re-open it if the issue still affects you with current releases. Regards, Lee
--- End Message ---
