[LU-12023] Tests should nto call modprobe directly Created: 27/Feb/19 Updated: 27/Feb/19 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.13.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Oleg Drokin | Assignee: | WC Triage |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
Some tests, namely conf-sanity 102, sanity-sec 31, lfsck-performance try to modprobe lustre modules directly which is not going to work when running out of build tree. There's load_module() function from test-framework.sh that should be used instead, though the semantic is somewhat different as it expects full path, but that's probably ok for our case since we know wher all the modules are and outside of the build tree it's smart enough to do modprobe |