Strange behavior with set_fact

Archives Ansible Project
1

Greetings,

I am having one really weird behavior that I cannot seem to be able to explain with set_fact.

Consider this YML file in one of my role:

https://gist.github.com/stelcheck/6866552

For some reason, if I try to run this on two machines, I get this (bootstrap set to false):

TASK: [If undefined set bootstrap to the first node of the cluster] ***********
<172.16.0.81> ESTABLISH CONNECTION FOR USER: vagrant
<172.16.0.80> ESTABLISH CONNECTION FOR USER: vagrant
ok: [node2.couchbase1.dev] => {“ansible_facts”: {“bootstrap”: “node1.couchbase1.dev”}, “item”: “”}
ok: [node1.couchbase1.dev] => {“ansible_facts”: {“bootstrap”: “node1.couchbase1.dev”}, “item”: “”}

TASK: [Check if the current machine is part of the cluster] **********************************************************
skipping: [node1.couchbase1.dev]

In fact, I can add a number of tasks after this set_fact and only the last task of the file will end up running on both servers (eg, skip node1 like in this example - and fail in one case since the register is_member wont be present in one case).

If I remove set_fact, all the tasks will run properly.

Anyone ever experienced this (using ansible 1.3.1)?

2

I do not see why this attribute would be skipped.

If you can pare this down to a minimum example (something that just uses “echo” maybe versus the site-specific shell command) I’d be happy to try to reproduce over here.

Please file a github ticket if you do so we don’t lose this.

Thanks!