James Cammarata 5b87951d6c Don't copy the parent block of TaskIncludes when loading statically ... When loading an include statically, we previously were simply doing a copy() of the TaskInclude object, which recurses up the parents creating a new lineage of objects. This caused problems when used inside load_list_of_blocks as the new parent Block of the new TaskInclude was not actually in the list of blocks being operated on. In most circumstances, this did not cause a problem as the new parent block was a proper copy, however when used in combination with PlaybookInclude (which copies conditionals to the list of blocks loaded) this untracked parent was not being properly updated, leading to tasks being run improperly. Fixes #18206		2016-11-11 08:09:43 -06:00
..
ansible	Don't copy the parent block of TaskIncludes when loading statically	2016-11-11 08:09:43 -06:00