# connection=local skips all remaining plays although only one host failed

**URL:** <https://forum.ansible.com/t/connection-local-skips-all-remaining-plays-although-only-one-host-failed/20360>\
**Category:** Ansible Project\
**Created:** [January 27, 2016, 12:53pm UTC](https://forum.ansible.com/t/connection-local-skips-all-remaining-plays-although-only-one-host-failed/20360 "2016-01-27T12:53:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jesse\_Schluter](https://avatars.discourse-cdn.com/v4/letter/j/f17d59/32.png) [@Jesse\_Schluter](https://forum.ansible.com/u/Jesse_Schluter)\
**Post date:** [January 27, 2016, 12:53pm UTC](https://forum.ansible.com/t/connection-local-skips-all-remaining-plays-although-only-one-host-failed/20360/1 "2016-01-27T12:53:39Z")

</div>

Hello everyone,

I have a small problem and I am not sure whether this is a bug or “works as defined”. We have a few Junos devices we are configuring and they require ansible\_connection=local, but since 2.0 if one of the hosts/inventory items fails, he does not simply skip this one host, but all. Here is a simple sample to simulate this behaviour without the need for a Junos host:

Inventory (where 10.118.194.22 is down):

[junos]  
10.118.194.11 ansible\_connection=local  
10.118.194.12 ansible\_connection=local  
10.118.194.21 ansible\_connection=local  
10.118.194.22 ansible\_connection=local

Playbook (as port use something that is reachable 😉 ):