[LU-17340] Interop sanity-sec test_31: lfs setquota -u quota_usr /mnt/lustre FAILED Created: 06/Dec/23 Updated: 08/Jan/24 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.15.4 |
| Fix Version/s: | Lustre 2.15.5 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Maloo | Assignee: | Sebastien Buisson |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| 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/f85e6e35-f5a1-4e54-8b31-4e4e3d7e07ab test_31 failed with the following error: /usr/bin/lfs setquota -u quota_usr -b 53856644 -B 56549476 -i 838864 -I 880807 /mnt/lustre FAILED! Test session details: <<Please provide additional information about the failure here>> enable quota as required CMD: onyx-70vm13 /usr/sbin/lctl get_param -n osd-ldiskfs.lustre-MDT0000.quota_slave.enabled CMD: onyx-70vm9 /usr/sbin/lctl get_param -n osd-ldiskfs.lustre-OST0000.quota_slave.enabled [HOST:onyx-70vm7.onyx.whamcloud.com] [old_mdt_qtype:none] [old_ost_qtype:none] [new_qtype:ug3] CMD: onyx-70vm13 /usr/sbin/lctl conf_param lustre.quota.mdt=ug3 CMD: onyx-70vm13 /usr/sbin/lctl conf_param lustre.quota.ost=ug3 Total disk size: 53855620 block-softlimit: 53856644 block-hardlimit: 56549476 inode-softlimit: 838864 inode-hardlimit: 880807 Setting up quota on onyx-70vm7.onyx.whamcloud.com:/mnt/lustre for quota_usr... + /usr/bin/lfs setquota -u quota_usr -b 53856644 -B 56549476 -i 838864 -I 880807 /mnt/lustre sanity-sec test_31: @@@@@@ FAIL: /usr/bin/lfs setquota -u quota_usr -b 53856644 -B 56549476 -i 838864 -I 880807 /mnt/lustre FAILED! VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV |
| Comments |
| Comment by Andreas Dilger [ 08/Dec/23 ] |
|
This test was modified in commit v2_15_55-156-gf70821fc14 patch https://review.whamcloud.com/50766 " Probably needs an ATM ticket to exclude this in interop testing with older clients. Not sure if it should also be skipped with new clients and old servers? Should a version check go into the test itself to skip servers < 2.15.55.156? Sebastien, could you please comment on the interop implications of your change. |
| Comment by Sebastien Buisson [ 08/Jan/24 ] |
|
There is also an issue with sanity-sec test_27a in interop testing, i.e. with earlier clients against latest servers. For both sanity-sec test_27a and test_31, the problem hit in interop testing is because of the tests themselves (correctness, cleanup).
I have created ATM-3021 to have these tests skipped in interop testing. |