Update playbook_executor.py

[sobngwi]

Wrong error message is display when the ansible-playbook command is lauch with the option option --start-at-task 'yy'

SUMMARY

I tried to import tasks in a play book with the import_tasks:

- name: yy
   import_tasks: import_tasks.yaml
   when: import_tasks_var is not defined

Here is the content of the file import_tasks.yaml:

- set_fact:
      import_tasks_var: foo

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

import_tasks

ADDITIONAL INFORMATION

Create a playbook named p1.yml with a task:

- name: yy
   import_tasks: import_tasks.yaml
   when: import_tasks_var is not defined

Here is the content of the file import_tasks.yaml:

- set_fact:
      import_tasks_var: foo

Run your play book p1.yml with option --start-at-task 'yy'

as import_tasks is static, the wrong message error below is displayed :

[ERROR]: No matching task "yy" found. Note: --start-at-task can only follow static includes.

 ansible-playbook p1.yml --step --start-at-task 'yy'

[mkrizek]

This is not really correct but the current wording is confusing (git blame'ed to my commit ;-) ).

I believe by "following static includes" it is meant that --start-at-task can target tasks within static includes.

So the message should be wordsmithed to contain the following information, --start-at-task:

• can target tasks within static includes
• cannot target tasks within dynamic includes
• can target the dynamic include task itself
• cannot target the static include task itself

[bcoca]

To explain the above, static includes (imports) are removed and replaced with the imported tasks when compiling the playbook so by the time you get here, they don't exist, but the imported tasks do exist.

On the contrary dynamic includes (include_X) exist at this point and have not been processed yet, so the 'future included tasks' are not accessible but the include itself is.