action #124631
Updated by jlausuch about 1 year ago
As of podman 4, we can make use of a network stack based on Netavark and Aardvark instead of former CNI: https://www.redhat.com/sysadmin/podman-new-network-stack However, Suse missed this and we are lacking those packages on our Hosts. There is an effort to push this to Factory: https://build.opensuse.org/package/show/devel:microos/netavark https://build.opensuse.org/package/show/devel:microos/aardvark-dns So, once these requests are accepted and we can install those packages, we should be able to use podman with that network stack. Packages to be installed: ``` zypper in netavark aardvark-dns ``` To do so, `/etc/containers/containers.conf` needs to be changed to: ``` [Network] network_backend="netavark" ``` and it's possible to check which network stack it's using: ``` podman info --format {{.Host.NetworkBackend}} {{ .Host.NetworkBackend }} ``` (by default it should be `cni`) We don't need to implement new tests with this, but do the change and then run podman network tests. Affected versions: > - 15-SP3 > - 15-SP4 > - 15-SP5 > - Tumbleweed > - Leap 15.4 > - Leap 15.3 ## Acceptance criteria - Extend podman_network.pm test module to switch the backend and run all the tests. - Enable this only for podman > 4.4.2