Closed 4ndyZ closed 3 weeks ago
@4ndyZ I can not reproduce with this task, it's also not runnable, we don't have systemd
option in pod. Can you please provide a real task you are running and see this problem?
Also please check you use actual 1.15.0 version: ansible-galaxy collection list | grep podman
Seems like the problem only if pod is generated by systemd: https://github.com/containers/podman/blob/main/pkg/systemd/generate/pods.go#L336-L338
startCommand = append(startCommand,
"pod", "create",
"--infra-conmon-pidfile", "{{{{.PIDFile}}}}",
"--pod-id-file", "{{{{.PodIDFile}}}}")
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
This issue reports an idempotency issue in collection version
>= 1.14.0
. Since the release1.14.0
the collection creates a change, when running in check mode and run mode while creating pods.Steps to reproduce the issue:
Create a playbook that creates a Podman pod
Run the playbook and create the Podman pod
Run the playbook again to create the Podman pod (in check or run mode, does not matter)
Describe the results you received: The playbook creates a change because the dynamic or auto set parameters
exit_policy
,infra_conmon_pidfile
andpod_id_file
changed.Describe the results you expected: No change and idempotency.
Additional information you deem important (e.g. issue happens only occasionally): None
Version of the
containers.podman
collection: Either git commit if installed from git:git show --summary
Or version fromansible-galaxy
if installed from galaxy:ansible-galaxy collection list | grep containers.podman
Output of
ansible --version
:Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Playbok you run with ansible (e.g. content of
playbook.yaml
):Command line and output of ansible run with high verbosity
Please NOTE: if you submit a bug about idempotency, run the playbook with
--diff
option, like:ansible-playbook -i inventory --diff -vv playbook.yml
Additional environment details (AWS, VirtualBox, physical, etc.): None