automation-tests/common/libnetwork/netavark
Paul Holzinger b0fc9a6550 libnetwork/netavark: allow same bridge name with different vlan
When a vlan is used there should be no bridge name conflict check. It is
totally valid to have the same bridge with different vlans in two
configs and that is the intended use case.

Fixes #2095

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
2025-01-30 19:28:24 +01:00
..
testfiles Fix typos across repo; extend codespell config 2024-01-03 23:38:47 +02:00
testplugin lint: update golangci-lint to v1.56.2 2024-03-05 18:10:32 +01:00
config.go libnetwork/netavark: allow same bridge name with different vlan 2025-01-30 19:28:24 +01:00
config_test.go libnetwork/netavark: allow same bridge name with different vlan 2025-01-30 19:28:24 +01:00
const.go chore: remove outdated build constraints 2024-01-03 22:56:00 +02:00
exec.go chore: replace 'interface{}' with 'any' for consistency 2024-01-08 21:26:34 +02:00
ipam.go libnetwork/netavark: remove ipam bucket on network rm 2024-04-03 18:19:57 +02:00
ipam_test.go update golangci-lint to 1.60.3 2024-09-03 15:57:02 +02:00
netavark_suite_test.go libnetwork/netavark: fix rootless unit tests 2024-06-25 11:39:33 +02:00
network.go libnetwork/netavark: do not create config dir in init 2024-12-09 14:18:30 +01:00
plugin_test.go lint: enable ginkgolinter 2024-03-18 11:51:54 +01:00
run.go libnetwork: add option to return rootless-netns ips 2024-05-16 15:24:52 +02:00
run_test.go lint: enable ginkgolinter 2024-03-18 11:51:54 +01:00