Details
-
Bug
-
Resolution: Fixed
-
Minor
-
Lustre 2.5.0
-
None
-
Build # 1687
OpenSFS cluster with combined MGS/MDS, single OSS with two OSTs, four clients; one agent (c07), one with robinhood/db running (c08) and just running as Lustre clients (c09, c10)
-
3
-
10782
Description
Test results at https://maloo.whamcloud.com/test_sessions/eb9d697c-2658-11e3-8d26-52540035b04c
metadata-updates fails with "attributes check failed". Node logs don't exist, but the suite_log shows:
Checking file(s) attributes ... c08: /lustre/scratch/d0.metadata-updates/c07/testfile [ uid gid size mode ] expected : 0 0 1024 0644 ; got : root 0 1024 0644 c08: Wrong file attributes c09: /lustre/scratch/d0.metadata-updates/c07/testfile [ uid gid size mode ] expected : 0 0 1024 0644 ; got : root 0 1024 0644 c09: Wrong file attributes pdsh@c10: c08: ssh exited with exit code 56 c07: /lustre/scratch/d0.metadata-updates/c07/testfile [ uid gid size mode ] expected : 0 0 1024 0644 ; got : root 0 1024 0644 c07: Wrong file attributes pdsh@c10: c09: ssh exited with exit code 56 pdsh@c10: c07: ssh exited with exit code 56 c10: /lustre/scratch/d0.metadata-updates/c07/testfile [ uid gid size mode ] expected : 0 0 1024 0644 ; got : root 0 1024 0644 c10: Wrong file attributes pdsh@c10: c10: ssh exited with exit code 56 metadata-updates : @@@@@@ FAIL: attributes check failed Trace dump: = /usr/lib64/lustre/tests/test-framework.sh:4264:error_noexit() = /usr/lib64/lustre/tests/metadata-updates.sh:227:main()
Although this was run during HSM testing, the copytool was not started and HSM was not enabled on the MDS, but all HSM attributes were in the test configuration files.