mirror of
https://github.com/kernelkit/infix.git
synced 2026-07-22 01:13:00 +02:00
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>
35 lines
1.1 KiB
Plaintext
35 lines
1.1 KiB
Plaintext
=== VETH Pair Between Two Containers
|
|
|
|
ifdef::topdoc[:imagesdir: {topdoc}../../test/case/containers/internal_link]
|
|
|
|
==== Description
|
|
|
|
Verify that a VETH pair can connect two containers directly, with *both*
|
|
ends handed to containers and neither remaining in the host namespace.
|
|
|
|
....
|
|
.------------. .------------.
|
|
| left | | right |
|
|
| veth0a ===|========= veth ===========|=== veth0b |
|
|
'------------' 10.0.0.1 10.0.0.2 '------------'
|
|
....
|
|
|
|
The pair is created in the host namespace then each end is moved into
|
|
its container when starting up. Connectivity is verified by pinging
|
|
across the pair, from inside one container's network namespace to the
|
|
other end's address.
|
|
|
|
==== Topology
|
|
|
|
image::topology.svg[VETH Pair Between Two Containers topology, align=center, scaledwidth=75%]
|
|
|
|
==== Sequence
|
|
|
|
. Set up topology and attach to target DUT
|
|
. Create VETH pair with both ends assigned to containers
|
|
. Verify both containers have started
|
|
. Verify {LEFT} reaches {RIGHT} over the internal VETH pair
|
|
. Remove containers and VETH pair, verify clean teardown
|
|
|
|
|