7:53 a.m.
On Tue, Nov 19, 2019 at 02:23:24PM +0100, Till Maas wrote:
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
It was
supposed to restore my network config after I ran the
integration test directly(not in container).
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
The desire state you mentioned try to set static IPv6 gateway with
DHCPv6 and Autoconf enabled which it not supported by nmstate yet.
https://github.com/nmstate/nmstate/pull/483
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.
We need if we want to support running outside of
docker.
Once test finished, we should restore the OS's network connection, so
that test report could report back to auto test system.
Kind regards
Till
--
Till Maas
--
Gris Ge