Details
-
Bug
-
Resolution: Fixed
-
Minor
-
Lustre 2.16.0
-
None
-
3
-
9223372036854775807
Description
This issue was created by maloo for S Buisson <sbuisson@ddn.com>
This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/e9a6e399-5436-4f4f-b3ce-037927b221ad
test_61 failed with the following error:
Timeout occurred after 294 minutes, last suite running was sanity-sec
Test session details:
clients: https://build.whamcloud.com/job/lustre-reviews/93375 - 4.18.0-348.7.1.el8_5.x86_64
servers: https://build.whamcloud.com/job/lustre-reviews/93375 - 4.18.0-348.23.1.el8_lustre.x86_64
The timeout occurs when trying to mount the client, once it has been added to nodemap 'c0'. But read-only is not enforced yet.
The problem is because of SSK in place, the key being used is not the right one.
VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity-sec test_61 - Timeout occurred after 294 minutes, last suite running was sanity-sec