Skip to content

Commit

Permalink
test/cni: work-around conntrack lingering rules
Browse files Browse the repository at this point in the history
If not enough time passes between the affinity and the perf test
(E.g. in the CI), the perf test fails on all CNIs (but Calico?) due
to lingering DNAT conntrack rules that map to old endpoints.

This seems a bug in either MetalLB or kubeproxy, as it points to
IP addresses that are not anymore valid.
  • Loading branch information
msune committed Oct 9, 2024
1 parent 4c20086 commit fea5981
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions test/cni/Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -110,6 +110,8 @@ _check_perf: _wait_up _wait_running
$(QUIET) for POD in $$(minikube kubectl -- get pods | grep my-nginx | awk '{print $$1}'); do \
while [[ "$$(minikube kubectl -- logs $$POD | grep 'Up and running...')" == "" ]]; do sleep 1; done; \
done;
$(QUIET) echo "Workaround lingering old conntrack (metallb/kubeproxy bug?)..."
$(QUIET) minikube ssh "sudo conntrack -F"
$(QUIET) echo "Launching iperf tests..."
set -o pipefail; \
NETNS=client ./perf/check_perf.sh 2>&1 | tee .last_perf_report.txt; \
Expand Down

0 comments on commit fea5981

Please sign in to comment.