You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Let's consider a pod created with containers.podman.podman_pod.
If the pod contains the property publish, then generating the systemd unit for this pod with generate_systemd after having added containers to that pod is going to remove the pod and the containers it contains.
Steps to reproduce the issue:
Create a pod using containers.podman.podman_pod and a publish property
Add one or several containers in the pod
Generate a systemd unit for that pod with generate_systemd
Describe the results you received:
I would expect the pod to run with the containers it contained and publish the ports on the host.
Describe the results you expected:
The pod is recreacted and the containers it contained are wiped.
Additional information you deem important (e.g. issue happens only occasionally):
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
For the sake of completeness I upgraded to the latest version of the collection using ansible-galaxy collection install --upgrade containers.podman, which upgraded to 1.10.3, and the same behaviour happens
Interestingly, if I add the (same) publish property to the generate_systemd task it doesn't remove the pod. I'm in a bit of a weird situation where I need to create the pod first so I can add containers to it, and I need to give it the exact same spec when I want to generate the systemd configuration… which can only happen after I've added the containers there :)
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Let's consider a pod created with
containers.podman.podman_pod
.If the pod contains the property
publish
, then generating the systemd unit for this pod withgenerate_systemd
after having added containers to that pod is going to remove the pod and the containers it contains.Steps to reproduce the issue:
containers.podman.podman_pod
and apublish
propertygenerate_systemd
Describe the results you received:
I would expect the pod to run with the containers it contained and publish the ports on the host.
Describe the results you expected:
The pod is recreacted and the containers it contained are wiped.
Additional information you deem important (e.g. issue happens only occasionally):
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
):This is the role I'm calling from my playbook
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
When running without the
publish
property, the output of the systemd generation task is:When running with the
publish
property, the output of the systemd unit generation task is:Additional environment details (AWS, VirtualBox, physical, etc.):
The target server is a RHEL9 on a VPS
The text was updated successfully, but these errors were encountered: