fix(#137): reap lab teardown residue (orphans in anonymous namespaces) #150
No reviewers
Labels
No labels
bug
deploy
documentation
duplicate
enhancement
good first issue
help wanted
invalid
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
femboy/blackwall!150
Loading…
Reference in a new issue
No description provided.
Delete branch "sp-fix-137-teardown"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes the systemic lab-teardown residue behind #137. Root cause (proven with live evidence): ~18 orphaned
blackwall-deception-interopprocesses were found running with an emptyip netns list— daemons survive teardown orphaned into anonymous (name-deleted) namespaces, invisible to anybw-*sweep, still holding ports/state. Caused bylab testbeing force-killed before itsDropteardown, anddown_alldeleting netns names before killing attached processes.Fix: kill-before-delete ordering (
ip netns pids <ns>→ kill, thennetns_del); a command-signature-scoped orphanpkillinlab down; idempotent host-inet blackwallnft/route clear; and a defensive pre-gatelab downin each CI step.Verified in CI: all 14 active gates pass with the hardening + pre-gate sweep (safe). Locally,
lab downreaps orphans and flowspec/rtbh/flow scenarios tear down clean (no leftover netns/orphans/host table).Gate re-enables deferred (kept
if: false): re-enabling the 4 quarantined gates revealed each has its OWN reliability issue, separate from the residue fix:Each needs dedicated per-gate work (tracked in #137/#88); this PR lands only the systemic residue fix, which is safe and green.
Gate: fmt + clippy
--deny warningsclean, workspace builds, coverage 95.46%, YAML valid.