docs update, interactive-on-error does trigger between nested tasks now

Signed-off-by: Andrew Schoen <aschoen@redhat.com>

diff --git a/README.rst b/README.rst
index c256dc122c7bfd6ddffd47785e4dd3608e8a6b10..d25a7ede3a4f8318cb96738b2adbe0aa82f98c93 100644 (file)
--- a/README.rst
+++ b/README.rst
@@ -283,12 +283,6 @@ chance to inspect the system -- both through Teuthology and via extra
 SSH connections -- and the cleanup completes only when you choose so.
 Just exit the interactive Python session to continue the cleanup.
 
-Note that this only catches exceptions *between* the tasks. If a task
-calls multiple subtasks, e.g. with ``contextutil.nested``, those
-cleanups *will* be performed. Later on, we can let tasks communicate
-the subtasks they wish to invoke to the top-level runner, avoiding
-this issue.
-
 Interactive task facilities
 ===========================