[LU-15675] Interop sanity-sec test_27a: fileset not taken into account Created: 22/Mar/22  Updated: 09/Dec/23

Status: Open
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.15.0, Lustre 2.15.3
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Maloo Assignee: Sebastien Buisson
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Related
is related to LU-17341 Interop sanity-sec test_55: test_55 f... Open
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for sarah <sarah@whamcloud.com>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/09838ea8-8c85-4a92-ba12-775d8994ed12

test_31 failed with the following error:

/usr/bin/lfs setquota -u quota_usr -b 13363604 -B 14031784 -i 838864 -I 880807 /mnt/lustre FAILED!

In interop testing between master and 2.14 client, sanity-sec test 31 and 35 failed with "Permission denied" in different operations.

in test_31

while umount  /mnt/lustre 2>&1 | grep -q busy; do
    echo /mnt/lustre is still busy, wait one second && sleep 1;
done;
fi
lsof: WARNING: can't stat() lustre file system /mnt/lustre
      Output information may be incomplete.
lsof: status error on /mnt/lustre: Permission denied
lsof 4.93.2
 latest revision: https://github.com/lsof-org/lsof

in test_35

CMD: onyx-50vm4 /usr/sbin/lctl get_param -n mdd.lustre-MDT0000.changelog_users
CMD: onyx-50vm4 /usr/sbin/lctl set_param mdd.*.changelog_mask=ALL
mdd.lustre-MDT0000.changelog_mask=ALL
mkdir: cannot create directory '/mnt/lustre/d35.sanity-sec': Permission denied
 sanity-sec test_35: @@@@@@ FAIL: failed to mkdir d35.sanity-sec 

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity-sec test_31 - /usr/bin/lfs setquota -u quota_usr -b 13363604 -B 14031784 -i 838864 -I 880807 /mnt/lustre FAILED!



 Comments   
Comment by Andreas Dilger [ 02/Feb/23 ]

Sebastien, it looks like this subtest is failing regularly during interop testing with "fileset not taken into account". Is this something to be concerned about, or something unexpected in the interop testing that should be skipped?

Could you please take a look.

Comment by Sebastien Buisson [ 03/Feb/23 ]

Yes, this can be due to a missing patch on b2_12, that aims at improving the test. I have ported it:
https://review.whamcloud.com/49891

Generated at Sat Feb 10 03:20:21 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.