-
-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
podman_container rebuilds container because it erroneously thinks network has changed #252
Labels
Comments
sshnaidm
added
bug
Something isn't working
bug/idempotency
Bug related to idempotency of modules
labels
May 6, 2021
Same issue here. Same versions.
|
Same here |
sshnaidm
added a commit
to sshnaidm/ansible-podman-collections
that referenced
this issue
Aug 2, 2021
sshnaidm
added a commit
to sshnaidm/ansible-podman-collections
that referenced
this issue
Aug 2, 2021
sshnaidm
added a commit
to sshnaidm/ansible-podman-collections
that referenced
this issue
Aug 2, 2021
sshnaidm
added a commit
to sshnaidm/ansible-podman-collections
that referenced
this issue
Aug 2, 2021
sshnaidm
added a commit
to sshnaidm/ansible-podman-collections
that referenced
this issue
Aug 2, 2021
sshnaidm
added a commit
to sshnaidm/ansible-podman-collections
that referenced
this issue
Aug 2, 2021
sshnaidm
added a commit
to sshnaidm/ansible-podman-collections
that referenced
this issue
Aug 2, 2021
sshnaidm
added a commit
to sshnaidm/ansible-podman-collections
that referenced
this issue
Aug 2, 2021
sshnaidm
added a commit
to sshnaidm/ansible-podman-collections
that referenced
this issue
Aug 2, 2021
sshnaidm
added a commit
to sshnaidm/ansible-podman-collections
that referenced
this issue
Aug 16, 2021
sshnaidm
added a commit
to sshnaidm/ansible-podman-collections
that referenced
this issue
Aug 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman_container
keeps wanting to recreate my container because it thinks my network has changed.Steps to reproduce the issue:
ansible-playbook test.yaml --diff
(playbook below) two or more times.Describe the results you received:
On the second run, container test2 is recreated.
Describe the results you expected:
Container test2 is not recreated on the second or successive runs.
Additional information you deem important (e.g. issue happens only occasionally):
With the playbook provided below the diff looks like:
Version of the
containers.podman
collection:Either git commit if installed from git:
git show --summary
Or version from
ansible-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.):
Running on FC 34 on bare metal.
The text was updated successfully, but these errors were encountered: