1
0
mirror of https://github.com/containers/netavark.git synced 2026-02-05 06:45:56 +01:00
Files
Paul Holzinger 49ee09b249 make network setup order deterministic
Change the file format of the networks json to use an array for the
PerNetworkOptions. With that we can get a defined order in which we
setup the networks and do that deterministically.

In order to provide backwards compatibility we use a custom json
deserializer function that accepts both the old and new format.
That allows us to still use the old podman against the new netavark
with this patch.

I also added PartialEq trait to the types so the unit test can compare
two loaded Networks.

I only converted a few of our test configs to the new format to keep the
diff smaller. We can convert most of them another time.

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
2025-12-05 14:08:46 +01:00
..
2025-11-12 14:13:33 +01:00
2024-06-25 13:20:54 +02:00
2023-05-22 15:10:53 +00:00
2025-01-10 18:08:42 +01:00
2025-11-17 19:02:16 +01:00
2025-11-17 19:02:16 +01:00

Netavark integration test with bats

Running tests

To run the tests locally in your sandbox, you can use one of these methods:

  • bats ./test/001-basic.bats # runs just the specified test
  • bats ./test/ # runs all

The tests need root privileges to create network namespaces, so you either have to run the test as root or in a user namespace. You can use podman unshare --rootless-netns bats test/ to run the tests as rootless user.

Requirements

  • jq
  • iproute2
  • firewalld
  • dbus-daemon