-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
None
-
3
-
9223372036854775807
lustre-initialization failed because the Lustre client modules were never loaded on one client node. The cluster did not come up, so no test ran.
Session: https://testing.whamcloud.com/test_sessions/cbfbf6f0-38f7-4209-998f-1055132f792f (review-dne-zfs-part-1, RHEL 10.1, trevis-156vm133..140)
Mount of the client trevis-156vm134:
2026-09-25T18:12:47 trevis-156vm134: mount.lustre: mount 10.240.46.238@tcp:/lustre at /mnt/lustre failed: No such device 2026-09-25T18:12:47 trevis-156vm134: Are the lustre modules loaded? 2026-09-25T18:12:47 Exit code: 19 2026-09-25T18:13:55 Auster exited unexpectedly
dmesg on trevis-156vm134 has no Lustre or LNet message at all, so lustre.ko was never loaded. The node's journal shows the provisioning job failing after boot:
Sep 25 18:08:06 trevis-156vm134 CROND[973]: (root) CMDOUT ([2026-09-25T18:08:06+00:00] FATAL: NoMethodError: undefined method `logger' for nil:NilClass)
This looks like a test-node setup problem, not a code problem. The same class was seen before on review-dne-zfs-part-2 and review-dne-zfs-part-6 (RHEL 10.1) in August 2026.