using "strategy: free" fixes the issue by ensuring the order of the execution. but it would increase the time of the execution, as execution will not be clubbed together for hosts having same var items.
default stragety (linear)
-------------------------
included: deployments.yaml for centos, localhost => (item=B)
included: deployments.yaml for centos, localhost => (item=C)
included: deployments.yaml for centos => (item=D)
included: deployments.yaml for localhost => (item=A)
with "strategy: free"
---------------------
included: deployments.yaml for centos => (item=B)
included: deployments.yaml for centos => (item=C)
included: deployments.yaml for centos => (item=D)
included: deployments.yaml for localhost => (item=A)
included: deployments.yaml for localhost => (item=B)
included: deployments.yaml for localhost => (item=C)
In the above example, the expected order for localhost is A, B, C.
using "strategy: free" fixes the issue by ensuring the order of the execution. but it would increase the time of the execution, as execution will not be clubbed together for hosts having same var items.
default stragety (linear) ------- ------- ----
-------
included: deployments.yaml for centos, localhost => (item=B)
included: deployments.yaml for centos, localhost => (item=C)
included: deployments.yaml for centos => (item=D)
included: deployments.yaml for localhost => (item=A)
with "strategy: free" ------- -------
-------
included: deployments.yaml for centos => (item=B)
included: deployments.yaml for centos => (item=C)
included: deployments.yaml for centos => (item=D)
included: deployments.yaml for localhost => (item=A)
included: deployments.yaml for localhost => (item=B)
included: deployments.yaml for localhost => (item=C)
In the above example, the expected order for localhost is A, B, C.