delegate_to not working with hosts not in inventory?

901 views
Skip to first unread message

Tim Rice

unread,
Dec 5, 2014, 8:14:13 AM12/5/14
to ansible...@googlegroups.com
Just upgraded to 1.8.2 and noticed a change in behavior (previosuly on 1.7.2)

delegate_to only works when the host we wnat to delegate to is in the current inventory, is this intentional? It was working fine on 1.7.2

Also, another delegate_to apparent change... we previously used 'delegate_to: "{{ nagios_server}}" ' to delegate to different hosts (nagios servers) when required.... this has also stopped working. it seems it doesnt evaluate the variable any more and attempts to use the string  "{{ nagios_server}}" as a host.

Thanks!

Tim Rice

unread,
Dec 5, 2014, 8:27:10 AM12/5/14
to ansible...@googlegroups.com
Can add that we have downgraded to 1.8.1 and both things appear to work fine..

James Cammarata

unread,
Dec 5, 2014, 9:43:35 AM12/5/14
to ansible...@googlegroups.com
Thanks Tim, there was a bugfix related to delegate_to in this release, which may have created this bug.  We'll look into this today.

On Fri, Dec 5, 2014 at 7:27 AM, Tim Rice <timr...@gmail.com> wrote:
Can add that we have downgraded to 1.8.1 and both things appear to work fine..

--
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 ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/6aa85194-dd24-47af-b51a-d347ec5f1027%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Michael DeHaan

unread,
Dec 5, 2014, 11:44:40 AM12/5/14
to ansible...@googlegroups.com
"delegate_to only works when the host we wnat to delegate to is in the current inventory, is this intentional? It was working fine on 1.7.2"

Ok, doesn't sound to be super breaking, but we're on it.  Thanks for the report.



Toshio Kuratomi

unread,
Dec 8, 2014, 5:13:37 PM12/8/14
to ansible...@googlegroups.com
Just committed a fix for this to devel that should fix both of these
problems. There was an initial fix last week which only fixed the
first problem. In case you're looking to patch your code, the new
fix[1]_ overwrites the previous one[2]_: so you'll need to apply it
manually


[1]_: https://github.com/ansible/ansible/commit/3269a349f32a2b5c1fc079a2d174e01c541f444b
[2]_: https://github.com/ansible/ansible/commit/b042fcc349f965a60943a3bfcf25f143b5fff3dc

-Toshio
> https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgxW8cqp_0F5%2BnqC3o75TaTFVbaFmvd9w2%2B1yh2msBFZiA%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages