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

sanity-selinux test_21a test_21b: c0.sepol not updated on mds1 after 20 secs

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.14.0
    • None
    • None
    • 3
    • 9223372036854775807

    Description

      This issue was created by maloo for Andreas Dilger <adilger@whamcloud.com>

      This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/73f9289e-3af0-11ea-b0f4-52540065bddc

      test_21b failed with the following error:

      c0.sepol not updated on mds1 after 20 secs
      

      VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
      sanity-selinux test_21a - c0.sepol not updated on mds1 after 20 secs
      sanity-selinux test_21b - c0.sepol not updated on mds1 after 20 secs

      Attachments

        Issue Links

          Activity

            [LU-13156] sanity-selinux test_21a test_21b: c0.sepol not updated on mds1 after 20 secs

            "Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/50400/
            Subject: LU-13156 tests: wait for nodemap update in sanity-selinux
            Project: fs/lustre-release
            Branch: b2_12
            Current Patch Set:
            Commit: b1c3382b2306b37b39749ef86dae299f5998ba01

            gerrit Gerrit Updater added a comment - "Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/50400/ Subject: LU-13156 tests: wait for nodemap update in sanity-selinux Project: fs/lustre-release Branch: b2_12 Current Patch Set: Commit: b1c3382b2306b37b39749ef86dae299f5998ba01

            "Etienne AUJAMES <eaujames@ddn.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/50400
            Subject: LU-13156 tests: wait for nodemap update in sanity-selinux
            Project: fs/lustre-release
            Branch: b2_12
            Current Patch Set: 1
            Commit: dc79dedfea4dbd46f1f9fcf2ac0c1e9f9ff25a6b

            gerrit Gerrit Updater added a comment - "Etienne AUJAMES <eaujames@ddn.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/50400 Subject: LU-13156 tests: wait for nodemap update in sanity-selinux Project: fs/lustre-release Branch: b2_12 Current Patch Set: 1 Commit: dc79dedfea4dbd46f1f9fcf2ac0c1e9f9ff25a6b
            pjones Peter Jones added a comment -

            Landed for 2.14

            pjones Peter Jones added a comment - Landed for 2.14

            Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/38034/
            Subject: LU-13156 tests: wait for nodemap update in sanity-selinux
            Project: fs/lustre-release
            Branch: master
            Current Patch Set:
            Commit: f1761cbe6b1243edd7a69c68c401d7285f7f3b38

            gerrit Gerrit Updater added a comment - Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/38034/ Subject: LU-13156 tests: wait for nodemap update in sanity-selinux Project: fs/lustre-release Branch: master Current Patch Set: Commit: f1761cbe6b1243edd7a69c68c401d7285f7f3b38

            Thanks to the testing carried out under https://review.whamcloud.com/37902, we can see that the problem hit with sanity-selinux test_21a and test_21b is due to primary MDS reboot/restart in prior tests launched in recovery-small, like test_23 or test_141.

            Because of such primary MDS reboot/restart, we need to make sure that nodemaps are properly updated on all nodes before using them.

            sebastien Sebastien Buisson added a comment - Thanks to the testing carried out under https://review.whamcloud.com/37902 , we can see that the problem hit with sanity-selinux test_21a and test_21b is due to primary MDS reboot/restart in prior tests launched in recovery-small, like test_23 or test_141. Because of such primary MDS reboot/restart, we need to make sure that nodemaps are properly updated on all nodes before using them.

            Sebastien Buisson (sbuisson@ddn.com) uploaded a new patch: https://review.whamcloud.com/38034
            Subject: LU-13156 tests: wait for nodemap update in sanity-selinux
            Project: fs/lustre-release
            Branch: master
            Current Patch Set: 1
            Commit: 164b0381dddbd3a81e614493d30b811f6297348a

            gerrit Gerrit Updater added a comment - Sebastien Buisson (sbuisson@ddn.com) uploaded a new patch: https://review.whamcloud.com/38034 Subject: LU-13156 tests: wait for nodemap update in sanity-selinux Project: fs/lustre-release Branch: master Current Patch Set: 1 Commit: 164b0381dddbd3a81e614493d30b811f6297348a

            Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/37899/
            Subject: LU-13156 tests: skip sanity-selinux test_21a+21b
            Project: fs/lustre-release
            Branch: master
            Current Patch Set:
            Commit: 8c1b62d09484161a40071c0aeecd1f1753d56870

            gerrit Gerrit Updater added a comment - Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/37899/ Subject: LU-13156 tests: skip sanity-selinux test_21a+21b Project: fs/lustre-release Branch: master Current Patch Set: Commit: 8c1b62d09484161a40071c0aeecd1f1753d56870

            Oops my bad. I totally misread this ticket

            You are right, this issue with sanity-selinux test_21a and test_21b is different from the one fixed by patch https://review.whamcloud.com/37224. Before patch https://review.whamcloud.com/37224, the client connection was working without sepol, which was not ok. Now that this patch has landed, we realize that sepol never gets updated, which is the source of the problem.

            I think it is ok to skip those 2 tests for now, as sepol is not widely used.

            sebastien Sebastien Buisson added a comment - Oops my bad. I totally misread this ticket You are right, this issue with sanity-selinux test_21a and test_21b is different from the one fixed by patch https://review.whamcloud.com/37224 . Before patch https://review.whamcloud.com/37224 , the client connection was working without sepol, which was not ok. Now that this patch has landed, we realize that sepol never gets updated, which is the source of the problem. I think it is ok to skip those 2 tests for now, as sepol is not widely used.

            The 37224 patch was landed on 2020-02-24, but these subtests are still failing regularly so there appears to be a different problem (maybe exposed once the configuration issue was resulted?) For example, patch https://review.whamcloud.com/37620 commit 1071a24b57a34dc87e704ac9cc99132700d0d0a5 is based on the current tip of master but still failed both of these tess.

            https://testing.whamcloud.com/test_sessions/461de6f9-30fe-4357-8088-489cd8295f29

            adilger Andreas Dilger added a comment - The 37224 patch was landed on 2020-02-24, but these subtests are still failing regularly so there appears to be a different problem (maybe exposed once the configuration issue was resulted?) For example, patch https://review.whamcloud.com/37620 commit 1071a24b57a34dc87e704ac9cc99132700d0d0a5 is based on the current tip of master but still failed both of these tess. https://testing.whamcloud.com/test_sessions/461de6f9-30fe-4357-8088-489cd8295f29

            Patch https://review.whamcloud.com/37224 was landed to fix sanity-selinux test_21a and test_21b, so they should not be skipped.

            sebastien Sebastien Buisson added a comment - Patch https://review.whamcloud.com/37224 was landed to fix sanity-selinux test_21a and test_21b, so they should not be skipped.

            People

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

              Dates

                Created:
                Updated:
                Resolved: