Guillaume Mulocher

Could be related to this: https://github.com/ansible/ansible/issues/75503

indeed - should have been fixed by: https://github.com/ansible/ansible/pull/78236

For the failing CI, it looks like we are hitting this: https://github.com/ansible/ansible/issues/71602 - the symptom is the same. The issue is that pylint itself is getting the warnings so I...

Adding what I posted on google chat here: So I did not have time to conduct extended testing - I was questioning in my first comment if using “non fqdn”...

@carlbuchmann looking at this reopned issue I think it was fixed by @emilarista as part of the A/A work: documentation: https://avd.sh/en/stable/roles/eos_cli_config_gen/index.html#port-channel-interfaces. PR fixing it https://github.com/aristanetworks/ansible-avd/pull/1780

Note that implementing this would need to add some modification in some of the BGP overlay logic where we explicitly disable some peer-groups in ipv4 address family which will be...

Requires formats - #2385

@MaheshGSLAB can you move the faiing test with ping avt in another PR and we will merge the 3 others?

FYI, building on previous answers in this thread, we ended up creating the following fixture to disable capsys on all invoke calls (truncated to simplify) ```python @pytest.fixture def click_runner(capsys: CaptureFixture[str])...

> _get_eos_validate_state_vars is being called twice per device when it could be run once for all devices. `for all` or `for each device`?