Thank you.  I did open an ansible github issue 
<https://github.com/ansible/ansible/issues/72611> and subsequently closed 
it based on respondents there.  Your comments above definitely helped.  
Seems 2.9.10 fixed "buggy behavior" that I was relying on by not explicitly 
using "connection: local".
On Friday, November 13, 2020 at 2:32:37 AM UTC-6 [email protected] wrote:

> On Thu, 12 Nov 2020 15:13:37 -0800 (PST)
> bill paxton <[email protected]> wrote:
>
> > I have a task that works fine for Ansible 2.9.7, but fails when I 
> upgrade 
> > to 2.10.3.
> > ...
> > Data could not be sent to remote host "localhost". Make sure this host 
> can 
> > be reached over ssh: ssh: connect to host localhost port 22: Cannot 
> assign 
> > requested address
>
> FWIW, I'm still on 2.9.6.
>
> As a hint, try to find out why *ssh* connection plugin is used to
> connect localhost. IMHO, the default is *local*. For example, testing
> with no configuration of the connection ("cat hosts | grep
> connection" shows nothing)
>
> shell> cat pb.yml
> - hosts: test_01
> tasks:
> - debug:
> var: ansible_connection
> - debug:
> var: ansible_connection
> delegate_to: localhost
>
> gives
>
> TASK [debug] ****
> ok: [test_01] =>
> ansible_connection: ssh
>
> TASK [debug]****
> ok: [test_01 -> localhost] =>
> ansible_connection: local
>
> See DEFAULT_TRANSPORT
>
> https://docs.ansible.com/ansible/latest/reference_appendices/config.html#default-transport
>
> "man ansible" says
>
> -v, --verbose
> verbose mode (-vvv for more, -vvvv to enable connection
> debugging)
>
> For example
>
> shell> ansible-playbook pb.yml -vvvv | grep connection
> connection: smart
> ansible_connection: ssh
> ansible_connection: local
>
> -- 
> Vladimir Botka
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/afad6ea3-0480-4314-8abc-d496625ede46n%40googlegroups.com.

Reply via email to