[LU-17949] Interop sanity-lnet test_220: load_lnet: command not found

• Type: Bug
• Resolution: Duplicate
• Priority: Minor
• Affects Version/s: Lustre 2.15.5
• Severity: 3
• Assignee: Etienne Aujames
• Reporter: Maloo

Description

This issue was created by maloo for sarah <[e-mail]>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/74fcc6b7-6239-4ab5-a0d6-23e4be81a7b0

test_220 failed with the following error:

Failed to load and configure LNet

Test session details:
clients: https://build.whamcloud.com/job/lustre-b2_15/87 - 4.18.0-477.10.1.el8_8.x86_64
servers: https://build.whamcloud.com/job/lustre-b2_14/2 - 4.18.0-240.1.1.el8_lustre.x86_64

<<Please provide additional information about the failure here>>

onyx-39vm2: /usr/sbin/lnetctl lnet configure --all
onyx-39vm3: rpc.sh: line 18: load_lnet: command not found
pdsh@onyx-39vm1: onyx-39vm3: ssh exited with exit code 127
 sanity-lnet test_220: @@@@@@ FAIL: Failed to load and configure LNet 

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity-lnet test_220 - Failed to load and configure LNet

Issue Links

• is related to: LU-17876 interop: sanity-lnet test_223: FAIL: Unable to enable routing
• is related to: LU-15595 Checking route aliveness should be a lookup rather than a calculation