This PR reproduces an error I discovered using this role in a loop since commit 3d03115a0df0d2e1bfae9cb854a8f0688b655733 which removes the following two tasks:
ensure "{{ service_name }}" is enabled at boot, and systemd reloaded
name: ensure "{{ service_name }}" is running
and uses handlers more extensively.
The following error is reported:
RUNNING HANDLER [podman-container-systemd : start service] *************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Could not find the requested service lighthttpd-2-container-pod-root.service: host"}
after running the first iteration (for lighthttpd-1).
The handler in iteration 1 in particular uses the variables from the second/last iteration.
This PR reproduces an error I discovered using this role in a loop since commit 3d03115a0df0d2e1bfae9cb854a8f0688b655733 which removes the following two tasks:
and uses handlers more extensively.
The following error is reported:
after running the first iteration (for lighthttpd-1).
The handler in iteration 1 in particular uses the variables from the second/last iteration.
I suspect this is because of the following fact:
I am looking for a solution for this problem. Any suggestions?