1.5 update - ansible-provisioning network_facts stopped working

[Oliver Heinz]

We are currently using some modules from the ansible-provsioning "project" https://github.com/ansible-provisioning.

It works fine with 1.4.x. When I upgrade to 1.5.x it runs into an error.

Task:

    - local_action: network_facts host='{{ inventory_hostname }}' inventory='/etc/ansible-provisioning/inventory/network-inventory.yml' full='yes'

gives:

TASK: [network_facts host='{{inventory_hostname}}' inventory='/etc/ansible-provisioning/inventory/network-inventory.yml' full='yes'] *** 

<127.0.0.1> PUT /etc/ansible-provisioning/inventory/network-inventory.yml TO network-inventory.yml

<127.0.0.1> EXEC ['/bin/sh', '-c', 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1398338832.84-154705207139639 && echo $HOME/.ansible/tmp/ansible-tmp-1398338832.84-154705207139639']

<127.0.0.1> PUT /tmp/tmpUgAUeZ TO /root/.ansible/tmp/ansible-tmp-1398338832.84-154705207139639/network_facts

<127.0.0.1> EXEC ['/bin/sh', '-c', '/usr/bin/python /root/.ansible/tmp/ansible-tmp-1398338832.84-154705207139639/network_facts; rm -rf /root/.ansible/tmp/ansible-tmp-1398338832.84-154705207139639/ >/dev/null 2>&1']

failed: [ansibletest.test.org] => {"failed": true}

msg: Inventory network-inventory.yml failed to transfer

FATAL: all hosts have already failed -- aborting

PLAY RECAP ******************************************************************** 

           to retry, use: --limit @/root/test.retry

ansibletest.test.org : ok=0    changed=0    unreachable=0    failed=1   

File /etc/ansible-provisioning/inventory/network-inventory.yml is copied to /etc/ansible-provisioning/network-inventory.yml

Is there any fundamental change that is know to create that behavior or do I need to debug that in detail? Maybe I just missed something when building/installing ansible and ansible-provisioning modules?

As I'm not a python developer  any hints where to look first for the problem  are more than welcome.

TIA,

Oliver

[Michael DeHaan]

Hi Oliver,

The "ansible provisioning" repo isn't affiliated with Ansible so this isn't the list for this.   You may file a ticket in that repo!

--
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/05741896-c624-4e42-9044-364cc1e92b6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Oliver Heinz]

Am Donnerstag, 24. April 2014 14:13:58 UTC+2 schrieb Michael DeHaan:

Hi Oliver,

The "ansible provisioning" repo isn't affiliated with Ansible so this isn't the list for this.   You may file a ticket in that repo!

Hello Michael,

I thought it might be a generic/know issue or a documented API change that  also affects other modules. But if no one here is aware of any similar problems it probably module specific.