[LU-12378] sanity-quota test 1 fails with 'project quota isn't released after deletion' Created: 03/Jun/19 Updated: 26/Jan/24 Resolved: 08/Jan/20 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.13.0 |
| Fix Version/s: | Lustre 2.14.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | James Nunez (Inactive) | Assignee: | Wang Shilong (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | DNE, LTS12, tests | ||
| Environment: |
DNE |
||
| Issue Links: |
|
||||||||||||||||||||||||
| Severity: | 3 | ||||||||||||||||||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||||||||||||||||||
| Description |
|
sanity-quota test_1 fails with 'project quota isn't released after deletion', yet, looking at the client test_log we see an issue with the test /usr/lib64/lustre/tests/sanity-quota.sh: line 637: [: [0]: integer expression expected From sanity-quota.sh test 1,
636 USED=$(getquota -p $TSTPRJID global curspace)
637 [ $USED -eq 0 ] || quota_error p $TSTPRJID \
638 "project quota isn't released after deletion"
We’ve seen two instances of this both for review-dne-part-4 at |
| Comments |
| Comment by James Nunez (Inactive) [ 03/Jun/19 ] |
|
Wang Shilong - would you please look into this issue? You were the last person to make a change to this line is saity-quota test 1. Thank you |
| Comment by Gerrit Updater [ 04/Jun/19 ] |
|
Wang Shilong (wshilong@ddn.com) uploaded a new patch: https://review.whamcloud.com/35052 |
| Comment by Gerrit Updater [ 14/Dec/19 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/35052/ |
| Comment by Peter Jones [ 14/Dec/19 ] |
|
Landed for 2.14 |
| Comment by Gerrit Updater [ 16/Dec/19 ] |
|
James Nunez (jnunez@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/37041 |
| Comment by Andreas Dilger [ 16/Dec/19 ] |
|
This patch is causing very frequent sanity-quota test_7b failures in autotest since it was landed on 2019-12-14. The patch failed 3x with the same test_7b failure on 2019-11-19 before it landed, and is the only patch that failed this way. |
| Comment by Wang Shilong (Inactive) [ 08/Jan/20 ] |
|
Andreas, i am supposing the failure is related to |
| Comment by Gerrit Updater [ 12/Feb/21 ] |
|
Etienne AUJAMES (eaujames@ddn.com) uploaded a new patch: https://review.whamcloud.com/41499 |