Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Using slirp4nets for pods is braking idempotency. This is similar to #184, which was about slirp4nets for containers only.
Steps to reproduce the issue:
Create pod using podman_pod and supply network mode with additional options
Create container belonging to that pod using podman_container
Rerun playbook without changing any parameters
Describe the results you received:
Pod and container are recreated. Ansible-playbook shows result of both tasks as 'changed'. Diff of pod contains the network options. There is no diff for the container.
Describe the results you expected:
Pod and container are not recreated. Ansible-playbook shows both tasks as 'ok'
Additional information you deem important (e.g. issue happens only occasionally):
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Using slirp4nets for pods is braking idempotency. This is similar to #184, which was about slirp4nets for containers only.
Steps to reproduce the issue:
Create pod using podman_pod and supply network mode with additional options
Create container belonging to that pod using podman_container
Rerun playbook without changing any parameters
Describe the results you received:
Pod and container are recreated. Ansible-playbook shows result of both tasks as 'changed'. Diff of pod contains the network options. There is no diff for the container.
Describe the results you expected:
Pod and container are not recreated. Ansible-playbook shows both tasks as 'ok'
Additional information you deem important (e.g. issue happens only occasionally):
Version of the
containers.podman
collection: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
Additional environment details (AWS, VirtualBox, physical, etc.):
Keeping the playbook simple, it creates the containers as root. However, same results for rootless mode.