New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Featured ansible_failed_task.host info on ansible_failed_task #48410
Comments
Hi @macklus, thank you for submitting this issue! |
Files identified in the description:
If these files are inaccurate, please update the |
Why not use e.g. |
!component =lib/ansible/playbook/block.py |
Files identified in the description: If these files are inaccurate, please update the |
@macklus This issue is waiting for your response. Please respond or the issue will be closed. |
@macklus You have not responded to information requests in this issue so we will assume it no longer affects you. If you are still interested in this, please create a new issue with the requested information. |
SUMMARY
when use block/rescue for Slack alerts on failures, if task is running on múltiple nodes, you dont know where the task fail. Added a ansible_failed_task.node should solve it.
ISSUE TYPE
COMPONENT NAME
code on block/rescue
ADDITIONAL INFORMATION
tag_Function_PrivatePhp contains 20 nodes.
The text was updated successfully, but these errors were encountered: