[LU-2567] Interop 2.3<->2.4 Failure on test suite lustre-initialization-1: quotacheck is not supported Created: 03/Jan/13 Updated: 14/Feb/17 Resolved: 14/Feb/17 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.3.0, Lustre 2.4.0, Lustre 2.4.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Maloo | Assignee: | Niu Yawei (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | MB, yuc2 | ||
| Severity: | 3 |
| Rank (Obsolete): | 5999 |
| Description |
|
This issue was created by maloo for sarah <sarah@whamcloud.com> This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/23c29e50-552e-11e2-8753-52540035b04c. The sub-test lustre-initialization_1 failed with the following error:
This is the interop testing between 2.3 client and 2.4 server, the quotacheck operation is not supported by 2.4 13:43:04:enable quota as required
13:43:04:CMD: client-32vm7 lctl get_param mdd.lustre-MDT*.quota_type
13:43:04:client-32vm7: error: get_param: /proc/{fs,sys}/{lnet,lustre}/mdd/lustre-MDT*/quota_type: Found no match
13:43:04:CMD: client-32vm8 lctl get_param obdfilter.lustre-OST*.quota_type
13:43:04:client-32vm8: error: get_param: /proc/{fs,sys}/{lnet,lustre}/obdfilter/lustre-OST*/quota_type: Found no match
13:43:04:[HOST:client-32vm2.lab.whamcloud.com] [old_quota_type:] [new_quota_type:ug3]
13:43:04:quotacheck failed: Operation not supported
13:43:04: auster : @@@@@@ FAIL: quotacheck has failed
|
| Comments |
| Comment by Peter Jones [ 04/Jan/13 ] |
|
Niu Could you please look into this one? Peter |
| Comment by Andreas Dilger [ 04/Jan/13 ] |
|
Would it be possible for the 2.4 lctl code to accept quotacheck and just print a message that it isn't needed anymore? That would probably allow the 2.3 test-framework to continue to work, and would also help users that are using quotacheck to figure things out. |
| Comment by Niu Yawei (Inactive) [ 04/Jan/13 ] |
|
Accepting quotacheck dosn't help for this case, since the t-f has to use a new measures to setup quota. Actually, we've fixed the t-f to not run quotacheck (but use new measures to setup quota) when interop with 2.4 servers, and the change has been ported to 2.1, 1.8 is on the way (http://review.whamcloud.com/#change,4897), but seems the port to 2.3 hasn't started yet. I'll port it soon. |
| Comment by Niu Yawei (Inactive) [ 04/Jan/13 ] |
|
Yujian told me that we'll not have 2.3.1, is it necessary to port this change to 2.3 anymore? |
| Comment by Andreas Dilger [ 05/Jan/13 ] |
|
The problem is that we automatically run 2.3+master interop tests on a regular basis. This would cause the 2.3 interop tests to always fail. My recommendation in the past has been to allow t-f patches to land on old feature branches to allow testing to continue working, and then run the interop tests using the branch instead of the release tag. Another longer-term alternative is to run the test-framework from the server for tests that are verifying server functionality. In both cases, this will not help today. I think Chris and Peter can hopefully better answer what our plans are for interop test issues like this. |
| Comment by Jodi Levi (Inactive) [ 15/Feb/13 ] |
|
Peter, can you comment on Andreas' question above? |
| Comment by Jian Yu [ 12/Aug/13 ] |
|
Lustre client: http://build.whamcloud.com/job/lustre-b2_3/41/ (2.3.0) The interop testing cannot be performed due to the issue in this ticket: |
| Comment by Jian Yu [ 03/Sep/13 ] |
|
Lustre client: http://build.whamcloud.com/job/lustre-b2_3/41/ (2.3.0) The interop testing cannot be performed due to the issue in this ticket: |
| Comment by Jian Yu [ 19/Dec/13 ] |
|
Lustre client: http://build.whamcloud.com/job/lustre-b2_3/41/ (2.3.0) The interop testing cannot be performed due to the issue in this ticket: |
| Comment by Andreas Dilger [ 14/Feb/17 ] |
|
Close old test issue. |