Files
Joachim Wiberg ddc57ed6ae confd: fix veth teardown regression
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>
2026-06-26 16:05:53 +02:00
..
2026-06-26 16:05:53 +02:00
2026-06-26 16:05:53 +02:00

=== Container with VETH Pair

ifdef::topdoc[:imagesdir: {topdoc}../../test/case/containers/veth]

==== Description

Verify connectivity with a simple web server container from behind a
regular bridge, a VETH pair connects the container to the bridge.

....
  .-------------.         .---------------.     .--------.
  |      | mgmt |---------| mgmt |        |     |  web-  |
  | host | data |---------| data | target |     | server |
  '-------------'         '---------------'     '--------'
                             |                    /
                            br0                  /
                              `----- veth0 -----'
....

==== Topology

image::topology.svg[Container with VETH Pair topology, align=center, scaledwidth=75%]

==== Sequence

. Set up topology and attach to target DUT
. Create 'web-br0-veth' container from bundled OCI image
. Verify container 'web-br0-veth' has started
. Verify basic DUT connectivity, host:data can ping DUT 10.0.0.2
. Verify container 'web-br0-veth' is reachable on http://10.0.0.2:91
. Remove container and VETH pair, verify clean teardown