Error: invalid or not allowed setting 'bridge-port': 'bridge-port' not among [connection, 802-3-ethernet (ethernet), 802-1x, dcb, sriov, ethtool, match, ipv4, ipv6, tc, proxy].\n", "name": "em1", "rc": 2}

[andreaskaris]

Since fecd7b2 we run into:

fatal: [hypervisor]: FAILED! => {"changed": false, "msg": "Error: invalid or not allowed setting 'bridge-port': 'bridge-port' not among [connection, 802-3-ethernet (ethernet), 802-1x, dcb, sriov, ethtool, match, ipv4, ipv6, tc, proxy].\n", "name": "em1", "rc": 2}

That seems to be related to:

ansible/ansible@5684dac

We are still installing on rhel 7.9 --- did you switch to rhel 8 and that's why this fails for us?

Thanks

[MaxBab]

Hi @andreaskaris ,

Yes, infrared moved to rhel 8.x in its support.
Please, start using rhel 8.x OS, and the issue will be solved.

[fhubik]

I'll try to clarify a bit more.

IR did not switch to RHEL8.x as that step would require all plugins and core to be branched or refactored to remove RHEL7.X related code/conditionals. That is not likely to happen as it would introduce risk and consume significant amount of resources for little gain. The more probable way is that IR (already is) will be supporting both versions (both as virthost version and vm node image), the difference is majority of deployments and underlying CI infra are currently shifted to RHEL8.x focus, which means also the IR maintenance shifted. That doesn't mean the supported is dropped.

Of course that doesn't mean RHEL7.x related flows can not be maintained by certain groups/community (I am aware of these still being deployed) who are using them, just it will likely possess more issues as the main focus/deployment pool shifted.