From deff045aa960236140e5c5b854fcef199e328d52 Mon Sep 17 00:00:00 2001 From: James Cammarata Date: Thu, 1 Oct 2015 10:04:22 -0400 Subject: [PATCH] Fix bug caused by options not having start_at_task when used through adhoc Fixes #12590 --- lib/ansible/executor/task_queue_manager.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/ansible/executor/task_queue_manager.py b/lib/ansible/executor/task_queue_manager.py index 087c2eb972..ae41afb600 100644 --- a/lib/ansible/executor/task_queue_manager.py +++ b/lib/ansible/executor/task_queue_manager.py @@ -210,7 +210,7 @@ class TaskQueueManager: # during initialization, the PlayContext will clear the start_at_task # field to signal that a matching task was found, so check that here # and remember it so we don't try to skip tasks on future plays - if self._options.start_at_task is not None and play_context.start_at_task is None: + if getattr(self._options, 'start_at_task', None) is not None and play_context.start_at_task is None: self._start_at_done = True # and run the play using the strategy