Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-15667

Interop sanity-quota test_52: FAIL: rename should fail

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • Lustre 2.15.0, Lustre 2.15.1, Lustre 2.15.3, Lustre 2.15.5
    • None
    • 3
    • 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/a1eccb5f-6cf5-49fd-ad9e-b4cede43b5b8

      test_52 failed with the following error:

      rename should fail
      
      == sanity-quota test 52: Rename across different project ID ========================================== 09:57:01 (1644400621)
      CMD: onyx-50vm4 /usr/sbin/lctl get_param -n version 2>/dev/null
      Waiting for local destroys to complete
      Creating test directory
      CMD: onyx-50vm3,onyx-50vm4 lctl set_param fail_val=0 fail_loc=0
      fail_val=0
      fail_loc=0
      fail_val=0
      fail_loc=0
      lfs project -sp 1 /mnt/lustre/d52.sanity-quota/dir
       sanity-quota test_52: @@@@@@ FAIL: rename should fail 
      

      VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
      sanity-quota test_52 - rename should fail

      Attachments

        Issue Links

          Activity

            [LU-15667] Interop sanity-quota test_52: FAIL: rename should fail

            Patch was deployed on 6/21

             

            colmstea Charlie Olmstead added a comment - Patch was deployed on 6/21  

            Charlie, can you please add an exception for sanity-quota test_52 that skips the test if the client version is b2_12 or b2_14. The relevant patch was landed in 2.15.0 and backported to b_es5_2 and b_es6_0, it is only the older branches that are affected.

            adilger Andreas Dilger added a comment - Charlie, can you please add an exception for sanity-quota test_52 that skips the test if the client version is b2_12 or b2_14. The relevant patch was landed in 2.15.0 and backported to b_es5_2 and b_es6_0, it is only the older branches that are affected.

            It looks like this is failing during interop testing because of patch https://review.whamcloud.com/45660 "LU-13176 mdd: rename file with different project ID" landing. That patch allows cross-project rename, when it was previously not allowed.

            However, when the test runs with an older client and newer server, the version check is not present in the old test, so the test fails. I'm not sure what can be done about that, since it isn't really a "protocol" change that causes problems, so no reason to have a connect flag for this (which is too late anyway), and we can't patch old releases.

            adilger Andreas Dilger added a comment - It looks like this is failing during interop testing because of patch https://review.whamcloud.com/45660 " LU-13176 mdd: rename file with different project ID " landing. That patch allows cross-project rename, when it was previously not allowed. However, when the test runs with an older client and newer server, the version check is not present in the old test, so the test fails. I'm not sure what can be done about that, since it isn't really a "protocol" change that causes problems, so no reason to have a connect flag for this (which is too late anyway), and we can't patch old releases.

            People

              colmstea Charlie Olmstead
              maloo Maloo
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: