test(e2e): unmanage the TAP anchors in the remaining kernel scenarios

Same guard the ethernet-switch scenario already carries: NetworkManager
can release an NM-managed TAP from its bridge shortly after
(re-)enslavement (docs/bugs/networkmanager-tap-release.md). Applied to
the Dynamips, QEMU, IOU, IOL-runner and switch-cascade scenarios after
their nodes have booted (no-op where nmcli/NetworkManager is absent).
This keeps those tests deterministic on un-declared hosts.
This commit is contained in:
YueGuobin committed 2026-10-06 00:21:11 +08:00
1 parent 28e9b82a5f
commit 15fbef93fb
5 files changed
+26

No files matched your search

@@ -111,6 +111,11 @@ def test_dynamips_kernel_datapath():
c1 = _boot(server, pid, r1_id)
c2 = _boot(server, pid, r2_id)
# NetworkManager can release an NM-managed TAP from its bridge after
# (re-)enslavement (docs/bugs/networkmanager-tap-release.md); take the
# anchors out of its reach for the rest of the run.
harness.unmanage_from_networkmanager(t1, t2)
# Kernel objects: anchors exist and the per-link bridge has exactly
# the two of them enslaved.
assert harness.tap_exists(t1) and harness.tap_exists(t2), (t1, t2)