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

Interop sanity-sec test_27a: fileset not taken into account

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • Lustre 2.15.0, 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/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!

      Attachments

        Issue Links

          Activity

            [LU-15675] Interop sanity-sec test_27a: fileset not taken into account

            This should be fixed in interop testing by the most recent ATM-3021 patch.

            adilger Andreas Dilger added a comment - This should be fixed in interop testing by the most recent ATM-3021 patch.

            This subtest should be skipped on interop testing with older branches.

            adilger Andreas Dilger added a comment - This subtest should be skipped on interop testing with older branches.
            adilger Andreas Dilger added a comment - - edited

            Sebastien, I'm seeing a lot of sanity-sec test_55 failures that are being attributed to this ticket:
            https://testing.whamcloud.com/search?status%5B%5D=FAIL&test_set_script_id=5984404e-4b34-11e0-a7f6-52540025f9af&sub_test_script_id=72320fcc-bee0-41a2-8f48-624be12babc9&start_date=2024-03-16&end_date=2024-03-22&source=sub_tests#redirect

            I'm not sure if this is the same issue, or if a new one should be opened? They are all failing testing with master servers, though some sessions with b_es6_0 clients are also failing, if that helps you isolate the issue.

            adilger Andreas Dilger added a comment - - edited Sebastien, I'm seeing a lot of sanity-sec test_55 failures that are being attributed to this ticket: https://testing.whamcloud.com/search?status%5B%5D=FAIL&test_set_script_id=5984404e-4b34-11e0-a7f6-52540025f9af&sub_test_script_id=72320fcc-bee0-41a2-8f48-624be12babc9&start_date=2024-03-16&end_date=2024-03-22&source=sub_tests#redirect I'm not sure if this is the same issue, or if a new one should be opened? They are all failing testing with master servers, though some sessions with b_es6_0 clients are also failing, if that helps you isolate the issue.

            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

            sebastien Sebastien Buisson added a comment - 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

            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.

            adilger Andreas Dilger added a comment - 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.

            People

              sebastien Sebastien Buisson
              maloo Maloo
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: