Skip to content
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

Role fails when jinja2_native=True #225

Closed
mcpovel opened this issue Oct 1, 2024 · 3 comments
Closed

Role fails when jinja2_native=True #225

mcpovel opened this issue Oct 1, 2024 · 3 comments

Comments

@mcpovel
Copy link
Contributor

mcpovel commented Oct 1, 2024

Describe the bug
When setting jinja2_native=True is set in ansible.cfg the role fails on several variables. First the repo key is converted from hex to decimal giving an invalid key 17394431339541615064.
Second the calculated port for galera_ist_recv_addr_port doews not work as string.
3rd the list galera_cluster_nodes contains the return "None" of append function for each host upfront of the actual node list.
This then fails with a hostvars['N'] not available.

To Reproduce
Set jinja2_native=True in ansible.,cfg and try to apply playbook.

Expected behavior
The playbook using the role should work with either setting of jinja2_native

Using ansible 9.1 and ansible core 2.16.1

@eRadical
Copy link
Collaborator

I might have some bandwidth to test this somewhere in the middle of November.

Meanwhile if you have a fix, feel free to create a PR.

@mcpovel
Copy link
Contributor Author

mcpovel commented Oct 29, 2024

Great, I am already trying to identify and work around some type issues.

@eRadical
Copy link
Collaborator

Closed via PR #232

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants