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
I expect that different dual-stack networks would have different subnets and gateway addresses both for IPv6 and IPv4.
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
$ ansible-galaxy collection install --force containers.podman
Process install dependency map
Starting collection install process
Installing 'containers.podman:1.6.1' to '/home/ivanov/.ansible/collections/ansible_collections/containers/podman'
Hmm... The same results with the command line. It occurrs both with podman 3.0.2-dev on CentOS 8.4, as with podman 3.2.2 on Fedora 34. It seems it's a podman bug.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Dual-stack networks created with
containers.podman.podman_network
module always have the same subnet and gateway address for IPv4.Steps to reproduce the issue:
(optional) Remove default podman network
Create first dual-stack network
Create second dual-stack network
Describe the results you received:
Both of dual-stack networks have the same subnet and gateway address for IPv4:
Describe the results you expected:
I expect that different dual-stack networks would have different subnets and gateway addresses both for IPv6 and IPv4.
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.):
Host machine with Ansible:
Virtual machine with Podman:
The text was updated successfully, but these errors were encountered: