with extra debugging:

The full traceback is:
Traceback (most recent call last):
  File
"/Users/dick.visser/foo/venv/lib/python3.11/site-packages/ansible/template/__init__.py",
line 1160, in do_template
    res = j2_concat(rf)
          ^^^^^^^^^^^^^
  File "<template>", line 764, in root
TypeError: 'NoneType' object is not iterable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File
"/Users/dick.visser/foo/venv/lib/python3.11/site-packages/ansible/plugins/action/template.py",
line 150, in run
    resultant = templar.do_template(template_data,
preserve_trailing_newlines=True, escape_backslashes=False)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File
"/Users/dick.visser/foo/venv/lib/python3.11/site-packages/ansible/template/__init__.py",
line 1171, in do_template
    raise AnsibleError("Unexpected templating type error occurred on (%s):
%s" % (to_native(data), to_native(te)))
ansible.errors.AnsibleError: Unexpected templating type error occurred on (
<huge template content>


I guessed that "line 764" would be the location in the template, but at
that place nothing seems relevant....

On Thu, 25 Jan 2024 at 15:08, Dick Visser <[email protected]> wrote:

> Hii,
>
> I have a template that has a lot of variables and control structures. I
> get an error during the playbook run:
>
> fatal: [prod_nagios2]: FAILED! => changed=false
>   msg: |-
>     AnsibleError: Unexpected templating type error occurred on (
>     <huge template content here>
> ): 'NoneType' object is not iterable
>
> The content of the template is 800 lines, about 36kB, with 100+ variables.
> Anyone have an idea where to start looking?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAF8BbLbdUE0ibKfai%2B3%2BKFfwv__oaVYT13gYnZua_5ibHSsy0w%40mail.gmail.com.

Reply via email to