action #160373
open
[containers] Make podman_netavark macvlan test independent of external DHCP server
Added by ph03nix 8 months ago.
Updated 23 days ago.
Description
Currently the podman macvlan test is dependent on an external DHCP server. We should change this test in such a way, that no external resources are required, e.g. by creating a virtual test network with a locally running DHCP server. I would recommend using dnsmasq as it is available on SLES and SLEM.
The motivation comes from failures like https://openqa.suse.de/tests/14288161/modules/podman_netavark/steps/130 but we saw similar issues also on s390x.
Acceptance criteria¶
- The
podman macvlan test only uses resources provided by the VM itself.
- Related to action #152194: Investigate failure of podman_netavark on s390x added
- Priority changed from Normal to High
- Status changed from Workable to In Progress
- Assignee set to mloviska
A challenging topic to unify the testing across all hypervisors. As of now, we use host-local mode, but the containers do not have access outside. I will come back to this later after more research
- Status changed from In Progress to Feedback
- Priority changed from High to Normal
Thank you Martin! Lowering priority for now.
- Subject changed from [podman] Make podman_netavark macvlan test independent of external DHCP server to [containers] Make podman_netavark macvlan test independent of external DHCP server
I haven't checked this in a while, but after Christmas time I will come back to it
mloviska wrote in #note-9:
I haven't checked this in a while, but after Christmas time I will come back to it
Thank you!
Also available in: Atom
PDF