search

redhat-openstack / infrared

Plugin based framework that aims to provide an easy-to-use CLI for Ansible based projects
https://infrared.readthedocs.io/en/latest/index.html
Apache License 2.0
100 stars 95 forks source link

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} #400

Open andreaskaris opened 3 years ago

andreaskaris commented 3 years ago

Since https://github.com/redhat-openstack/infrared/commit/fecd7b238976e708600e697df084c1bd35f9632d 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:

https://github.com/ansible/ansible/pull/68065/commits/5684dacb35585b773393f165054933c2351bd4ce

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

Thanks

MaxBab commented 3 years ago

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 commented 3 years ago

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.