From: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
To: khorenko@virtuozzo.com
Cc: devel@openvz.org
Subject: [Devel] [PATCH hci-8.1 v2 1/1] selftests: bonding: do not build on the namespaces of a killed run
Date: Mon, 28 Sep 2026 22:46:46 +0300 [thread overview]
Message-ID: <20260928194708.553135-2-eva.kurchatova@virtuozzo.com> (raw)
In-Reply-To: <20260928194708.553135-1-eva.kurchatova@virtuozzo.com>
A lag test run that is killed, by the suite timeout for one, leaves
lag_node1 and lag_node2 behind, and the next run builds on them: the
veth is renamed into a namespace that already has an eth0, the kernel
warns about a partly applied link change, and the bond never comes
back:
TEST: mode (2) bond recovery [FAIL]
Bond failed to recover
The failure is intermittent, which makes it look like a timing problem.
Delete the leftover namespaces before creating them.
https://virtuozzo.atlassian.net/browse/VSTOR-139651
Feature: fix selftests
Signed-off-by: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
---
tools/testing/selftests/drivers/net/bonding/lag_lib.sh | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/drivers/net/bonding/lag_lib.sh b/tools/testing/selftests/drivers/net/bonding/lag_lib.sh
index bf9bcd1b5ec0..3710acd2f8d9 100644
--- a/tools/testing/selftests/drivers/net/bonding/lag_lib.sh
+++ b/tools/testing/selftests/drivers/net/bonding/lag_lib.sh
@@ -90,8 +90,9 @@ lag_setup2x2()
local state=${1:-down}
local namespaces="lag_node1 lag_node2"
- # create namespaces
+ # A killed run leaves the namespaces behind, start clean
for n in ${namespaces}; do
+ ip netns del ${n} 2>/dev/null
ip netns add ${n}
done
--
2.55.0
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-09-28 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 19:46 [Devel] [PATCH hci-8.1 v2 0/1] " Eva Kurchatova
2026-09-28 19:46 ` Eva Kurchatova [this message]
2026-09-30 14:14 ` Konstantin Khorenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260928194708.553135-2-eva.kurchatova@virtuozzo.com \
--to=eva.kurchatova@virtuozzo.com \
--cc=devel@openvz.org \
--cc=khorenko@virtuozzo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.