Closed ulvida closed 2 years ago
The role still works on my laptop, where:
ulvida@qhispy:~/tech/interior/config$ ansible --version
ansible 2.10.8
config file = /home/ulvida/tech/interior/config/ansible.cfg
configured module search path = ['/home/ulvida/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python3/dist-packages/ansible
executable location = /usr/bin/ansible
python version = 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110]
It may come from ansible version.
Debugging, I saw that "{{ bind9_zones_dynamic }} + {{ bind9_zones_static }}"
was no longer producing the expected result of the union of the two zones' lists. I solved it replacing this expression by:
with_items:
- '{{ bind9_zones_dynamic | union( bind9_zones_static ) }}'
I test and submit it in our next PR.
Debugging, I saw that
"{{ bind9_zones_dynamic }} + {{ bind9_zones_static }}"
was no longer producing the expected result of the union of the two zones' lists.
This solution also solves the problem:
with_items:
- '{{ bind9_zones_dynamic + bind9_zones_static }}'
thx
Exploring tests, I realized that my debian PC, while updated to bullseye, was still using python 2.7 as default for python command. When I did the switch, bind9 role stopped working, failing without any change in configuration in this task:
My evironement is: