mirror of
https://github.com/ansible/awx.git
synced 2026-03-24 20:35:02 -02:30
59bd73bff8
* We trigger notifications when the callback receiver processes the playbook_on_stats event. This is the last event in ansible-playbook and the process should exist very shortly after this event is emitted. The trouble comes in with the isolated node feature. There is a management playbook that runs periodically that pulls the events from the remote node. It's possible that the management playbooks runs, gets the playbook_on_stats event, but does not see that the playbook is finished running. Therefore the job status is still seen as 'running' BUT we have kicked of the notification for the job. The notification worker will enter a loop waiting on the job to enter the finished state. In this case the time it takes for the job to enter the finished state can be long, roughly 2 * the management playbook run time. * This new setting allows the user to increase the time that the notification spends waiting for the job to enter the finished state.