-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
None
-
3
-
9223372036854775807
sanity-lnet test_150 (and the other import tests that compare "lnetctl export --backup" with the export after "lnetctl import") fails when an unrelated node talks to the test node while the test runs.
Failed test set: https://testing.whamcloud.com/test_sets/e8847e09-1bb6-4fdf-acf5-63a62d52a203 (session 0f99ad1c-e041-4bb0-99aa-f2d364661605, lustre-reviews 134096, el8.10 review-ldiskfs, 2026-10-21)
The test configures eth0 (10.240.46.152@tcp), runs "lnetctl export --backup" as the expected output, unconfigures, and imports the ip2nets yaml. The expected output carries a peer section the import cannot reproduce:
peer:
- primary nid: 10.240.46.149@tcp
Multi-Rail: true
peer ni: - nid: 10.240.46.149@tcp
10.240.46.149 is not one of the four test nodes of the session. The node console shows it connecting to this node earlier in the suite: "LNetError: Refusing connection from 10.240.46.149 for 10.240.46.152@tcp: No matching NI". So inbound traffic from a foreign node created a peer entry between "net add" and "export", and the actual output after import (a fresh lnet configure) has no such peer. Nothing in the test fails to import.
The test should compare only the net and global sections, or export only those (lnetctl export --backup with peers filtered out), rather than requiring an empty peer table on a shared subnet.
Seen once in about 13900 sanity-lnet suite runs over 30 days.
Raised by Patch Watcher run pw-engineer-69735-ps3-b2ff6565fcd6 on https://review.whamcloud.com/69735
VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity-lnet test_150 - test_150 failed with 1