Richard Megginson

> > The information about how to install and invoke an example using ansible-playbook is already given at [linux-system-roles.github.io](https://linux-system-roles.github.io/) , > > Wouldn't it be better to build on that...

> Hello. I think I just hit this: > > ``` > TASK [linux-system-roles.network : Install packages] ***************************************************************************************************************************************************************************************** > Wednesday 02 March 2022 11:12:06 +0100 (0:00:00.064) 0:00:12.621 ******* > fatal:...

> > That might be difficult, and probably unhelpful, if there are a couple of dozen variables required that are usually provided by `setup` or `gather_facts: true`. > > I...

Every role has (or should have) a preamble like this in the tasks/main.yml - https://github.com/linux-system-roles/kernel_settings/blob/master/tasks/main.yml#L2-L15 for example ```yaml - name: Set version specific variables include_vars: "{{ lookup('first_found', ffparams) }}" vars:...

> What's the next step here? Do you have suggestions how to address this? We don't have any suggestions yet. We noticed this in collections testing and didn't want to...

> Regarding the tree structure, I suppose the tests can be adjusted to detect whether it is a role or collection structure and import files respectively. Yes, something like that....

> Since the tests directly test the python code, moving the files around should not affect the tests. The conversion to collections *rewrites the python code* - specifically, the import...

> Thank you for the report. Could this be something new in the ansible 2.13? We are running various ansible versions for some time (currently 2.12 in github actions) and...

@nhosoi This looks like a 2.13 porting issue - might be an issue with jinja 3 as well - maybe ansible-core 2.13 or jinja 3 is more type strict? I'm...

This looks like a bug in jinja 3.0.3. If I run with ansible-core-2.13 and jinja 3.0.3 I see the error. If I use jinja latest (3.1.2) I do not see...