[LU-15363] Don't use lustre modules to test LNet with sanity-lnet

• Type: Improvement
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.15.0
• Affects Version/s: Lustre 2.15.0
• Assignee: James A Simmons
• Reporter: James A Simmons

Description

A few sanity-lnet test were failing for the native Linux client. The reason for this is by default the LNet stack is initialized with LNET_PID_ANY which doesn't automatically setup LNet with the module parameters. Currently sanity-lnet works around this by loading the lustre modules which initialize the LNet stack with LNET_PID_LUSTRE which does properly setup the lnet stack. This doesn't work for the native Linux client since Lustre doesn't start the LNet at module loading but mounting which sanity-lnet doesn't do.

Issue Links

• is related to: LU-12511 Prepare lustre for adoption into the linux kernel