From 04bfbb14d6dbe274f755862417bc7ee608c6724e Mon Sep 17 00:00:00 2001 From: tom-clx Date: Wed, 27 Sep 2017 16:57:42 -0500 Subject: [PATCH] Update playbooks_blocks.rst (#24069) * Update playbooks_blocks.rst The rescue section documentation should be clear that successful completion of a rescue section will override other error handling behavior. * more precise rescue docs explains in detail the consequences of successful rescue --- docs/docsite/rst/playbooks_blocks.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/docsite/rst/playbooks_blocks.rst b/docs/docsite/rst/playbooks_blocks.rst index b28ec505360..3d64f568fba 100644 --- a/docs/docsite/rst/playbooks_blocks.rst +++ b/docs/docsite/rst/playbooks_blocks.rst @@ -61,7 +61,8 @@ Blocks also introduce the ability to handle errors in a way similar to exception The tasks in the ``block`` would execute normally, if there is any error the ``rescue`` section would get executed with whatever you need to do to recover from the previous error. The ``always`` section runs no matter what previous -error did or did not occur in the ``block`` and ``rescue`` sections. +error did or did not occur in the ``block`` and ``rescue`` sections. It should be noted that the play continues if a +``rescue`` section completes successfully as it 'erases' the error status (but not the reporting), this means it won't trigger ``max_fail_percentage`` nor ``any_errors_fatal`` configurations but will appear in the playbook statistics. Another example is how to run handlers after an error occurred :