# delegate\_to does not work for array of hosts passed in to role **URL:** \ **Category:** Ansible Project\ **Created:** [June 2, 2015, 3:37am UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376 "2015-06-02T03:37:38Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Barry\_Kaplan](https://avatars.discourse-cdn.com/v4/letter/b/48db29/32.png) [@Barry\_Kaplan](https://forum.ansible.com/u/Barry_Kaplan)\ **Post date:** [June 2, 2015, 3:37am UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/1 "2015-06-02T03:37:38Z")
I posted this as a bug ([https://github.com/ansible/ansible/issues/11102](https://github.com/ansible/ansible/issues/11102)). But it was closed saying it was a discussion. Not sure why, seems like a clear bug to me. But I’m open to be dissuaded. ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [June 2, 2015, 1:26pm UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/2 "2015-06-02T13:26:32Z")
> From the output of the 3rd task it seems that mongodb\_replica\_set\_hosts[0] is being interpreted as '{' which, of course, does not resolve. This does not seem to be an array issue but of too many nested templating attempts. ---
**Author:** ![Barry\_Kaplan](https://avatars.discourse-cdn.com/v4/letter/b/48db29/32.png) [@Barry\_Kaplan](https://forum.ansible.com/u/Barry_Kaplan)\ **Post date:** [June 2, 2015, 4:16pm UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/3 "2015-06-02T16:16:31Z")
What do you think would be causing the nested templating? Something deep in variable resolution? The third echo is the direct version of first setting the value to a fact, which works. ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [June 2, 2015, 4:34pm UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/4 "2015-06-02T16:34:01Z")
not sure what 'works' means in this context ---
**Author:** ![Barry\_Kaplan](https://avatars.discourse-cdn.com/v4/letter/b/48db29/32.png) [@Barry\_Kaplan](https://forum.ansible.com/u/Barry_Kaplan)\ **Post date:** [June 2, 2015, 4:43pm UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/5 "2015-06-02T16:43:08Z")
“works” is that the third task delegates to the same host as the second task. Don’t you expect the exact same output for the last two tasks? Are you seeing something that I am missing? ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [June 2, 2015, 4:54pm UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/6 "2015-06-02T16:54:47Z")
the task fails with e 'fatal', what looks the same is the verbose output of what will be executed ---
**Author:** ![Barry\_Kaplan](https://avatars.discourse-cdn.com/v4/letter/b/48db29/32.png) [@Barry\_Kaplan](https://forum.ansible.com/u/Barry_Kaplan)\ **Post date:** [June 3, 2015, 1:49am UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/7 "2015-06-03T01:49:44Z")
`2) ssh ... -o ConnectTimeout=10 10.0.139.56 /bin/sh -c ... 3) ssh ... -o ConnectTimeout=10 { /bin/sh -c ...` So you don’t think that the ssh ip in the 3 task should not be the same as 2? I’m sorry Brian, but I am not all following what the miscommunication is here. ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [June 3, 2015, 3:24am UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/8 "2015-06-03T03:24:02Z")
the ssh ip in task 3 is '{' which indicates that the [0] is applied to the 'template string' and not to the resulting array you expect. This makes the 3rd task fail as it cannot ssh to '{'. ---
**Author:** ![Barry\_Kaplan](https://avatars.discourse-cdn.com/v4/letter/b/48db29/32.png) [@Barry\_Kaplan](https://forum.ansible.com/u/Barry_Kaplan)\ **Post date:** [June 3, 2015, 3:55am UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/9 "2015-06-03T03:55:58Z")
Exactly. Is that a mistake I am making? Or a bug? I filed the bug because I don’t see a mistake on my part. ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [June 3, 2015, 4:01am UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/10 "2015-06-03T04:01:17Z")
can you show that variable in a debug during execution? it does not look like it is being set properly. ---
**Author:** ![Barry\_Kaplan](https://avatars.discourse-cdn.com/v4/letter/b/48db29/32.png) [@Barry\_Kaplan](https://forum.ansible.com/u/Barry_Kaplan)\ **Post date:** [June 4, 2015, 12:02pm UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/11 "2015-06-04T12:02:04Z")
Here’s the new test: ` - set\_fact: mongodb\_candidate\_master: “{{mongodb\_replica\_set\_hosts[0]}}” run\_once: true - name: var groups.mongod\_rs\_member[0] debug: var=groups.mongod\_rs\_member[0] run\_once: true - shell: echo “HELLO groups.mongod\_rs\_member +++++++++++++++++” delegate\_to: “{{groups.mongod\_rs\_member[0]}}” run\_once: true - name: var mongodb\_candidate\_master debug: var=mongodb\_candidate\_master run\_once: true - shell: echo “HELLO mongodb\_candidate\_master +++++++++++++++++” delegate\_to: “{{mongodb\_candidate\_master}}” run\_once: true - name: var mongodb\_replica\_set\_hosts[0] debug: var=mongodb\_replica\_set\_hosts[0] run\_once: true - name: msg mongodb\_replica\_set\_hosts[0] debug: msg=“{{mongodb\_replica\_set\_hosts[0]}}” run\_once: true - debug: msg=“{{mongodb\_replica\_set\_hosts[0]}}” run\_once: true - shell: echo “HELLO mongodb\_replica\_set\_hosts +++++++++++++++++” delegate\_to: “{{mongodb\_replica\_set\_hosts[0]}}” run\_once: true ` And the output: ` ansible❯ ansible-playbook -i inventory/aws/staging playbooks/configure/mongod.yml --skip-tags base ops/git/master !+ PLAY [Base ansible configuration (packages)] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* GATHERING FACTS \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ok: [10.0.137.189] ok: [10.0.139.51] ok: [10.0.136.46] PLAY [Base ansible configuration (configure)] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* GATHERING FACTS \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ok: [10.0.137.189] ok: [10.0.139.51] ok: [10.0.136.46] PLAY [Base ansible configuration (users)] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* GATHERING FACTS \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ok: [10.0.137.189] ok: [10.0.139.51] ok: [10.0.136.46] PLAY [Configure mongodb replicaset cluster] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* GATHERING FACTS \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ok: [10.0.136.46] ok: [10.0.137.189] ok: [10.0.139.51] TASK: [debug var=groups.mongod\_rs\_member] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ok: [10.0.136.46] =\> { “var”: { “groups.mongod\_rs\_member”: [ “10.0.136.46”, “10.0.139.51”, “10.0.137.189” ] } } ok: [10.0.139.51] =\> { “var”: { “groups.mongod\_rs\_member”: [ “10.0.136.46”, “10.0.139.51”, “10.0.137.189” ] } } ok: [10.0.137.189] =\> { “var”: { “groups.mongod\_rs\_member”: [ “10.0.136.46”, “10.0.139.51”, “10.0.137.189” ] } } TASK: [mongodb | set\_fact] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ok: [10.0.136.46] TASK: [mongodb | var groups.mongod\_rs\_member[0]] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ok: [10.0.136.46] =\> { “var”: { “groups.mongod\_rs\_member[0]”: “10.0.136.46” } } TASK: [mongodb | shell echo “HELLO groups.mongod\_rs\_member +++++++++++++++++”] \*\*\* changed: [10.0.136.46 → 10.0.136.46] TASK: [mongodb | var mongodb\_candidate\_master] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ok: [10.0.136.46] =\> { “var”: { “mongodb\_candidate\_master”: “10.0.136.46” } } TASK: [mongodb | shell echo “HELLO mongodb\_candidate\_master +++++++++++++++++”] \*\*\* changed: [10.0.136.46 → 10.0.136.46] TASK: [mongodb | var mongodb\_replica\_set\_hosts[0]] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ok: [10.0.136.46] =\> { “var”: { “mongodb\_replica\_set\_hosts[0]”: “10.0.136.46” } } TASK: [mongodb | msg mongodb\_replica\_set\_hosts[0]] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ok: [10.0.136.46] =\> { “msg”: “10.0.136.46” } TASK: [mongodb | debug msg=“{”] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ok: [10.0.136.46] =\> { “msg”: “10.0.136.46” } TASK: [mongodb | shell echo “HELLO mongodb\_replica\_set\_hosts +++++++++++++++++”] \*\*\* fatal: [10.0.136.46 → {] =\> SSH Error: data could not be sent to the remote host. Make sure this host can be reached over ssh FATAL: all hosts have already failed – aborting ` The last debug is interesting. I does not have a -name and it seems to render the value as ‘{’ just like the delegate\_to. ---
**Author:** ![Barry\_Kaplan](https://avatars.discourse-cdn.com/v4/letter/b/48db29/32.png) [@Barry\_Kaplan](https://forum.ansible.com/u/Barry_Kaplan)\ **Post date:** [July 16, 2015, 11:08am UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/12 "2015-07-16T11:08:14Z")
Is it still unclear Brian? I also seem to be seeing a related problem. Consider: ` - name: Provision Ops RDS instance hosts: localhost connection: local gather\_facts: no tags: [control] tasks: … - shell: | echo {{groups.consul\_server[0]}} && hostname -i && curl localhost:8500/v1/catalog/services register: \_\_catalog delegate\_to: groups.consul\_server[0] ` Here the shell commands runs on localhost, not the host specified. The output is `TASK: [shell echo {{groups.consul_server[0]}} && hostname -i && curl localhost:8500/v1/catalog/services ] *** REMOTE_MODULE command echo 10.0.196.116 && hostname -i && curl localhost:8500/v1/catalog/services #USE_SHELL EXEC ['/bin/sh', '-c', 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1437044596.27-54518627543713 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1437044596.27-54518627543713 && echo $HOME/.ansible/tmp/ansible-tmp-1437044596.27-54518627543713'] PUT /tmp/tmpTGBlM3 TO /home/bkaplan/.ansible/tmp/ansible-tmp-1437044596.27-54518627543713/command EXEC ['/bin/sh', '-c', u'LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 /usr/bin/python /home/bkaplan/.ansible/tmp/ansible-tmp-1437044596.27-54518627543713/command; rm -rf /home/bkaplan/.ansible/tmp/ansible-tmp-1437044596.27-54518627543713/ >/dev/null 2>&1'] failed: [localhost -> groups.consul_server[0]] => {"changed": true, "cmd": "echo 10.0.196.116 && hostname -i && curl localhost:8500/v1/catalog/services", "delta": "0:00:00.012358", "end": "2015-07-16 16:33:16.332372", "rc": 7, "start": "2015-07-16 16:33:16.320014", "warnings": []} stderr: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to localhost port 8500: Connection refused stdout: 10.0.196.116 127.0.1.1` Where ‘10.0.196.116’ is groups.consul\_server[0]. So the variable resolves correctly, but delegate to does not seem to use it. This is not specific to shell, it has the same behavior for other modules (eg, uri). ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [July 17, 2015, 12:02am UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/13 "2015-07-17T00:02:28Z")
you need moustaches: delegate\_to: "{{groups.consul\_server[0]}}" only conditionals (when: ) do not need templating, with\_ has a haphazard support for it which we plan to deprecate. ---
**Author:** ![Barry\_Kaplan](https://avatars.discourse-cdn.com/v4/letter/b/48db29/32.png) [@Barry\_Kaplan](https://forum.ansible.com/u/Barry_Kaplan)\ **Post date:** [July 17, 2015, 3:11am UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/14 "2015-07-17T03:11:33Z")
Hmm, thought I tried that, but will check. Thanks Brian. I wonder whether it would be better for it to be error if delegate\_to does not resolve rather than silently fall back to localhost… Depending on the task fallback to localhost could do some serious damage. ---
**Author:** ![Barry\_Kaplan](https://avatars.discourse-cdn.com/v4/letter/b/48db29/32.png) [@Barry\_Kaplan](https://forum.ansible.com/u/Barry_Kaplan)\ **Post date:** [July 17, 2015, 4:53am UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/15 "2015-07-17T04:53:37Z")
I see the same behavior with the moustaches: ` - name: Test delegate to shell: echo “{{ groups.consul\_server[0] }}” && hostname -i register: \_\_hostname delegate\_to: “{{ groups.consul\_server[0] }}” - debug: var=\_\_hostname ` ` TASK: [Test delegate to] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* \<10.0.196.116\> REMOTE\_MODULE command echo “10.0.196.116” && hostname -i #USE\_SHELL \<10.0.196.116\> EXEC [‘/bin/sh’, ‘-c’, ‘mkdir -p $HOME/.ansible/tmp/ansible-tmp-1437108695.64-26819269533917 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1437108695.64-26819269533917 && echo $HOME/.ansible/tmp/ansible-tmp-1437108695.64-26819269533917’] \<10.0.196.116\> PUT /tmp/tmpDXWJFH TO /home/bkaplan/.ansible/tmp/ansible-tmp-1437108695.64-26819269533917/command \<10.0.196.116\> EXEC [‘/bin/sh’, ‘-c’, u’LANG=en\_US.UTF-8 LC\_CTYPE=en\_US.UTF-8 /usr/bin/python /home/bkaplan/.ansible/tmp/ansible-tmp-1437108695.64-26819269533917/command; rm -rf /home/bkaplan/.ansible/tmp/ansible-tmp-1437108695.64-26819269533917/ \>/dev/null 2\>&1’] changed: [localhost → 10.0.196.116] =\> {“changed”: true, “cmd”: “echo "10.0.196.116" && hostname -i”, “delta”: “0:00:00.004458”, “end”: “2015-07-17 10:21:35.693136”, “rc”: 0, “start”: “2015-07-17 10:21:35.688678”, “stderr”: “”, “stdout”: “10.0.196.116\n127.0.1.1”, “warnings”: } TASK: [debug var=\_\_hostname] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ok: [localhost] =\> { “var”: { “\_\_hostname”: { “changed”: true, “cmd”: “echo "10.0.196.116" && hostname -i”, “delta”: “0:00:00.004458”, “end”: “2015-07-17 10:21:35.693136”, “invocation”: { “module\_args”: “echo "10.0.196.116" && hostname -i”, “module\_name”: “shell” }, “rc”: 0, “start”: “2015-07-17 10:21:35.688678”, “stderr”: “”, “stdout”: “10.0.196.116\n127.0.1.1”, “stdout\_lines”: [ “10.0.196.116”, “127.0.1.1” ], “warnings”: } } } ` ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [July 17, 2015, 2:22pm UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/16 "2015-07-17T14:22:49Z")
well, the first difference is that you are not delegating to a host named 'groups.consul\_server[0]' but to 10.0.196.116 Sorry for not noticing before, but the delegate\_to on debug is irrelevant, debug always executes on 'the master' or machine you execute ansible on, it does not need to connect to any machine, i'm not sure what you are expecting there. delegate\_to on shell or any module that executes remotely goes to the delegated server, but things that operate on 'master' like debug, prompt, add\_host, group\_by make no sense to delegate. ---
**Author:** ![Barry\_Kaplan](https://avatars.discourse-cdn.com/v4/letter/b/48db29/32.png) [@Barry\_Kaplan](https://forum.ansible.com/u/Barry_Kaplan)\ **Post date:** [July 18, 2015, 2:49am UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/17 "2015-07-18T02:49:37Z")
Brian, I’m not following you at all. It was the shell command that uses the delegate\_to. The debug is only showing the register from the shell. ` - name: Test delegate to shell: echo “{{ groups.consul\_server[0] }}” && hostname -i register: \_\_hostname delegate\_to: “{{ groups.consul\_server[0] }}” - debug: var=\_\_hostname ` `"stdout_lines": ["10.0.196.116", <--- echo "{{ groups.consul_server[0] }}" "127.0.1.1" <--- hostname -i ],` ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [July 18, 2015, 2:52am UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/18 "2015-07-18T02:52:01Z")
ah, formatting of previous email threw me off, the only reason i can think of for this happening is that you have connection=local for the task (from play or command line) and the host does not have it specified through ansible\_connection. ---
**Author:** ![Barry\_Kaplan](https://avatars.discourse-cdn.com/v4/letter/b/48db29/32.png) [@Barry\_Kaplan](https://forum.ansible.com/u/Barry_Kaplan)\ **Post date:** [July 20, 2015, 5:05am UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/19 "2015-07-20T05:05:48Z")
All my hosts come from the ec2 inventory plugin. I can access the hosts in all other ways without having to explicitly specify an ansible\_connection. So then is it better to specify the target host in the play and use local\_action? I kinda thought thesetwo were inverses of each other. -barry ---
**Author:** ![Barry\_Kaplan](https://avatars.discourse-cdn.com/v4/letter/b/48db29/32.png) [@Barry\_Kaplan](https://forum.ansible.com/u/Barry_Kaplan)\ **Post date:** [July 24, 2015, 5:46am UTC](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376/20 "2015-07-24T05:46:02Z")
Perfect! I have removed the connection=local from the play and now all works as expected. I guess I don’t fully understand why connection=local should be used. When I was first starting with ansible plays that I studied that did ec2 stuff used it, so I did too. [Next page](https://forum.ansible.com/t/delegate-to-does-not-work-for-array-of-hosts-passed-in-to-role/18376.md?page=2)