Details
-
Bug
-
Resolution: Fixed
-
Minor
-
Lustre 2.14.0
-
Lustre clients >= 2.13.57.12 and Lustre servers with version < 2.13.57.12
-
3
-
9223372036854775807
Description
sanity-sec test_55 landed to the master, future 2.14.0, branch on 13 DEC 2020 with patch 355787745f21 (“LU-14121 nodemap: do not force fsuid/fsgid squashing”). Test 55 started failing on 17 DEC 2020 for interop testing; Lustre clients >= 2.13.57.12 and Lustre servers with version < 2.13.57.12.
Looking at the suite_log for the failure at https://testing.whamcloud.com/test_sets/869af2e1-1bbb-412c-bcd1-54da574ffa5b, we see
Started clients trevis-19vm1.trevis.whamcloud.com: CMD: trevis-19vm1.trevis.whamcloud.com mount | grep /mnt/lustre' ' 10.9.4.227@tcp:/lustre on /mnt/lustre type lustre (rw,flock,user_xattr,lazystatfs,noencrypt) open: Permission denied Initially root ruid:rgid 0:0, euid:egid 0:0 Groups 0 - root, To switch to effective sanityusr uid:gid 500:500 Groups 500 - sanityusr, Now root ruid:rgid 0:0, euid:egid 500:500 Groups 500 - sanityusr, sanity-sec test_55: @@@@@@ FAIL: test_55 failed with 13 Trace dump: = /usr/lib64/lustre/tests/test-framework.sh:6273:error() = /usr/lib64/lustre/tests/test-framework.sh:6576:run_one()
We probably just need to add a check at the beginning of sanity-sec test 55 that the Lustre server version >=2.13.57.12 to fix this issue.