Bug L2 interfaces & Channel_Groups set wtih lacp_fallback

[ryanmerolle]

Issue Summary

Link #542 given the relation.

When channel_groups are set, no other L2 config is applied which is useful to eliminate L2 redudant config. The problem is when you set LACP fallback individual on the bond, you need to be able to set config parameters on the port.

Why do people need to set fallback? PIXE Boot...

Which component(s) of AVD impacted

eos_cli_config_gen

How do you run AVD ?

Ansible AWX

Steps to reproduce

set channel_group on an interface & lacp_fallback on its associated Port-Channel.

Relevant log output

No response

Contributing Guide

• I agree to follow this project's Code of Conduct

[ryanmerolle]

2 options:

• Just remove the logic put in place to minimize redundant ethernet interface config since ethernet_interfaces currently have no way of being aware of the port-channel having a fallback configuration - Easy fix, but sort of a breaking change in given everyone who is unware of this current logic would see a ton of redundant config generated once they update to the version that includes the fix
• Leverage the port_channel_interfaces dictionary to find the parent portchannel and determine if lacp_fallback is configured. Then leverage in the ethernet_interfaces logic with regards to generating the currently hidden config. - Not that hard, but you need to think of data input checks to make sure a parent port-channel exists. Eliminates the breaking change I mentioned above.