docker_network with multiple subnets always changes #65815
Labels
affects_2.9
This issue/PR affects Ansible v2.9
bug
This issue/PR relates to a bug.
cloud
docker
has_pr
This issue has an associated PR.
module
This issue/PR relates to a module.
python3
support:community
This issue/PR relates to code supported by the Ansible community.
SUMMARY
When using
docker_network
to create a network with multiple subnets, the task will delete/create the network even if it already exists with the correct subnets. Ansible fails to judge if the existing subnets are correct, probably because of the way the arrays of subnets are compared in python.ISSUE TYPE
COMPONENT NAME
docker_network
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
Both systems are running ArchLinux.
STEPS TO REPRODUCE
also vars:
EXPECTED RESULTS
I was expecting to run the play 10 times and get Changed only on the first run and OK on the other 9 runs.
ACTUAL RESULTS
The docker network ALWAYS changes, even if the subnets are correct on the server, causing all docker containers on the network to disconnect. This will cause downtime for all the services that run on the node.
The text was updated successfully, but these errors were encountered: