# Ansible 2.0 : question about facts applied to delegated host

**URL:** <https://forum.ansible.com/t/ansible-2-0-question-about-facts-applied-to-delegated-host/19840>\
**Category:** Ansible Project\
**Created:** [November 24, 2015, 1:45pm UTC](https://forum.ansible.com/t/ansible-2-0-question-about-facts-applied-to-delegated-host/19840 "2015-11-24T13:45:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ludovic\_Petetin](https://avatars.discourse-cdn.com/v4/letter/l/f14d63/32.png) [@Ludovic\_Petetin](https://forum.ansible.com/u/Ludovic_Petetin)\
**Post date:** [November 24, 2015, 1:45pm UTC](https://forum.ansible.com/t/ansible-2-0-question-about-facts-applied-to-delegated-host/19840/1 "2015-11-24T13:45:56Z")

</div>

Hello,

We have a question about an Ansible 2 change.

In the V2 changelog, we can see “Now when you delegate an action that returns ansible\_facts, these facts will be applied to the delegated host, unlike before when they were applied to the current host”

We think it may have a big impact for us.

Because on our side, we have several custom modules for EC2 and Proxmox which gather facts for a server and which use directly BOTO or Proxmox REST API from the server where Ansible is installed so we call these modules with a “delegate\_to 127.0.0.1”.

Moreover, we use these modules in several contexts, especially in several cases where servers are not UP (to start VM, to update some configuration, etc…) where we MUST delegate to avoid SSH timeout.

If the fact is applied to 127.0.0.1, the current play\_hosts won’t be able to access them which is a big problem for us.

So, will there be a way to keep the current behaviour ?

Thanks,

Ludo

---

<div class="post-metadata">

**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:** [November 24, 2015, 4:11pm UTC](https://forum.ansible.com/t/ansible-2-0-question-about-facts-applied-to-delegated-host/19840/2 "2015-11-24T16:11:53Z")

</div>

Hi,

This was already brought to our attention by several users, it was a  
case I had missed when asking for the feature.

For now we are removing the feature for 2.0 and will bring it back in  
2.1 with a configurable flag that defaults to the current behavior.  
You will see the change in RC2.