# Ansible Network Automation - Issue Rendering Jinja2 Template - Invalid input

**URL:** <https://forum.ansible.com/t/ansible-network-automation-issue-rendering-jinja2-template-invalid-input/45109>\
**Category:** Get Help\
**Tags:** template, templating, network, galaxy-ng\
**Created:** [January 14, 2026, 9:31pm UTC](https://forum.ansible.com/t/ansible-network-automation-issue-rendering-jinja2-template-invalid-input/45109 "2026-01-14T21:31:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![IPvSean](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ipvsean/32/1153_2.png) [@IPvSean](https://forum.ansible.com/u/IPvSean)\
**Post date:** [January 14, 2026, 9:31pm UTC](https://forum.ansible.com/t/ansible-network-automation-issue-rendering-jinja2-template-invalid-input/45109/1 "2026-01-14T21:31:25Z")

</div>

Recent community reports around Ansible network automation stem from a regression introduced in ansible-core 2.19 related to how network `*_config` modules handle templating of the `src` parameter. Historically, some network modules supported inline Jinja2 templating directly within src (for example, `src: template.j2`). In ansible-core 2.19, Ansible language enhancements changed some underlying behaviors used during network configuration generation. Several network collections depended on the previous behavior, which led to breakage when those assumptions changed.

```auto
   - name: Apply configuration from template
     arista.eos.eos_config:
       src: template.j2

```

Ansible engineering has put out a fix, if you are running ansible-core 2.19 you can just upgrade ansible.netcommon

```auto
ansible-galaxy collection install ansible.netcommon --upgrade

```

There is more info on this knowledge base article: [Ansible Network Automation - Issue Rendering Jinja2 Template - Invalid input - Red Hat Customer Portal](https://access.redhat.com/solutions/7136399)