If you mistakenly believe using `ansible-runner` is too much work, then you can instead do even more work to put your tasks in blocks with `rescue` and `always` sections to record the data which you can later collate. See https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_blocks.html#handling-errors-with-blocks for details.
If you can live with less fine-grained information - i.e. not down to the task level - then familiarize yourself with `RETRY_FILES_ENABLED` and `RETRY_FILES_SAVE_PATH`. See `ansible-config list` for details on those. These tell Ansible to list the hosts which failed a run in the designated file. Another possibility that fits sort of in-between the first two is to insert a `run_once: true` task at select points in your playbook to compare the `ansible_play_hosts_all` and `ansible_play_hosts` lists to see how they differ. The difference will be the hosts which have failed at that point. The effectiveness of this method depends on the `strategy` your plays employ. In other words, all hosts' task executions have to be in-sync at the time this `run_once` task runs. (I have not experimented with this. Nor with the other suggestions either.) On Thursday, March 9, 2023 at 7:16:50 PM UTC-5 Vladimir Botka wrote: > See https://ansible-runner.readthedocs.io/en/stable/ > > The artifacts will keep data to create the report. > > > -- > Vladimir Botka > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/351b1582-8aa9-44ca-a654-33f8f3edaa45n%40googlegroups.com.
