7:23 a.m.
Hi,
in
https://github.com/nmstate/nmstate/blob/master/tests/integration/conftest...
there is a fixture to restore the Nmstate state after test runs. This
happens unconditionally for all interfaces and causes failures when
Nmstate does not actually support setting the reported state. I saw
this so far with podman when there is a tap interface in the container
that made it choke. Also it fails on other systems:
https://nmstate.atlassian.net/browse/NMSTATE-275
Do we really need it like this? Can we at least limit it to only eth1
and eth2? AFAIU it will not remove any left-over profiles from the
tests anyhow so eth1 and eth2 would be the only interfaces that are
affected by this. But AFAIU, the tests fixtures clean up eth1/eth2
also all the time already.
Kind regards
Till
--
Till Maas
He/His/Him
Ansible RHEL Networking System Role Maintainer
Red Hat GmbH, https://www.redhat.com/de, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael O'Neill, Tom Savage, Eric Shander