mirror of
https://github.com/kernelkit/infix.git
synced 2026-07-22 01:13:00 +02:00
Joachim Wiberg
ddc57ed6ae
When a veth pair has one end in a container and the other in the host
namespace, removing it failed: the container end's teardown deleted the
whole pair, so the host end's own delete then failed ("Cannot find
device") and aborted the teardown, leaving the interface behind.
The host-namespace delete added for the both-ends-in-container case was
emitted for every container veth end. Restrict it to the primary end,
which for a host/container pair is the host end that already deletes the
pair itself.
Extend the container veth tests to remove the pair and verify it is gone,
covering both the single-end (regression) and both-ends teardown paths.
Fixes: #1546
Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
:testgroup: == Containers Tests verifying link:https://opencontainers.org/[OCI container] support: - Basic web server container running in host network mode - Container enable/disable functionality via configuration - Container environment variable configuration and access - Common setup with docker0 bridge and automatic VETH pairs - Connecting containers with VETH pairs to standard Linux bridges - Assigning physical Ethernet interfaces to containers - Container upgrades with persistent volume data - Container upgrade using RPC with cleanup of old image - Firewall container running in host network mode with full privileges include::basic/Readme.adoc[] <<< include::enabled/Readme.adoc[] <<< include::environment/Readme.adoc[] <<< include::bridge/Readme.adoc[] <<< include::phys/Readme.adoc[] <<< include::veth/Readme.adoc[] <<< include::volume/Readme.adoc[] <<< include::upgrade/Readme.adoc[] <<< include::firewall_basic/Readme.adoc[] <<< include::host_commands/Readme.adoc[]