-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Lustre 2.15.0
-
None
-
SLES15 SP2 clients
-
3
-
9223372036854775807
sanity-sec test_51 started failing with 'setcap CAP_CHOWN' on 06 APRIL 2021 with Lustre 2.14.51.42 for SLES15 SP2 only. This test fails for SLES12 SP5 clients about 72% of the time.
Looking at the logs of a recent failure at https://testing.whamcloud.com/test_sets/4657f55b-3160-4093-b9f4-ebad90cd2943, we see the test output in the suite_log
== sanity-sec test 51: FS capabilities =============================================================== 09:20:25 (1627982425) running as uid/gid/euid/egid 500/500/500/500, groups: [/mnt/lustre/d51.sanity-sec/chown] [500] [/mnt/lustre/d51.sanity-sec/f51.sanity-sec] /mnt/lustre/d51.sanity-sec/chown: changing ownership of '/mnt/lustre/d51.sanity-sec/f51.sanity-sec': Operation not permitted /usr/lib64/lustre/tests/sanity-sec.sh: line 3730: setcap: command not found sanity-sec test_51: @@@@@@ FAIL: setcap CAP_CHOWN Trace dump: = /usr/lib64/lustre/tests/test-framework.sh:6220:error() = /usr/lib64/lustre/tests/sanity-sec.sh:3730:test_51()
There are several instances of this failure:
https://testing.whamcloud.com/test_sets/534c4bf0-6c5d-40df-bce0-4180178a7bdf
https://testing.whamcloud.com/test_sets/cdc2cff3-bc35-4441-8be9-1342d0959e26
https://testing.whamcloud.com/test_sets/5a151fe2-83a9-41cc-a323-2f288c4cb532