Ansible Facts/variables not saving multi-host play debug to a file about ansible HOT 8 CLOSED

Files identified in the description:

None

If these files are incorrect, please update the component name section of the description or use the component bot command.

from ansible.

This is not a bug. You are attempting to update a file multiple times simultaneously, so at least one update will make it into the file but some may not (depending on the exact timing of when each module execution reads and writes the file, which will vary between playbook runs.)

You should either template the entire file at once, or make sure you only run one lineinfile: task at a time (e.g. by using serial: or throttle:)

from ansible.

Closing per above.

If you have further questions please stop by IRC or the mailing list:

• IRC: #ansible on irc.libera.chat
• mailing list: https://groups.google.com/forum/#!forum/ansible-project

from ansible.

This is not a bug. You are attempting to update a file multiple times simultaneously, so at least one update will make it into the file but some may not (depending on the exact timing of when each module execution reads and writes the file, which will vary between playbook runs.)

You should either template the entire file at once, or make sure you only run one lineinfile: task at a time (e.g. by using serial: or throttle:)

Thats interesting, throttle made it consistent

from ansible.

You have to take into account that Ansible is parallel by default, but this does not lock files as the basic assumption is that the parallelism will affect different hosts. So if you want to do something like this you can use several solutions (some already explained above):

• a callback (see the included tree callback)
• a task with run: once and a template that writes the file in one shot
• a play that runs on localhost
• a task with throttle: 1, can keep lineinfile
• a play with serial: 1, can keep lineinfile

from ansible.

You have to take into account that Ansible is parallel by default, but this does not lock files as the basic assumption is that the parallelism will affect different hosts. So if you want to do something like this you can use several solutions (some already explained above):
* a task with run: once and a template that writes the file in one shot
* a play that runs on localhost

These 2 did not work for me. The race condition still messed with the variables being written to the file.

from ansible.

There should be no race conditions as both only apply to a single host and hence only one fork.

from ansible.

When i tried it, it did not work. both template and/or localhost did not work

from ansible.