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

Autotest doesn't install OSD packages when using fstype=mem

Details

    • Improvement
    • Resolution: Done
    • Minor
    • None
    • None
    • None
    • 4
    • 3
    • 9223372036854775807
    • ATM-DCO Weeks 50-51

    Description

      Autotest doesn't install the OSD packages for the in-memory OSD. Instead, it appears to default to installing only ldiskfs. For example, see https://testing.whamcloud.com/test_logs/70b4678d-7f48-4e27-acc4-f7691bb4e47f/show_text. I used `rpm -qa` to list all installed packages - and I only see ldiskfs OSD packages:

      kmod-lustre-osd-ldiskfs-2.16.50_88_gad94a0a-1.el8.x86_64

      lustre-osd-ldiskfs-mount-2.16.50_88_gad94a0a-1.el8.x86_64

      Notably, the $FSTYPE environment variable is set correctly. To reproduce this, copy https://review.whamcloud.com/c/fs/lustre-release/+/55594 revision 22. This version of patch includes the OSD along with the debugging I added. For test parameters, I used:

      Test-Parameters: trivial fstype=mem testlist=sanity

      Attachments

        Issue Links

          is blocking

          New Feature - A new feature of the product, which has yet to be developed. LU-17995 In-memory OSD device

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Activity

            [LU-18545] Autotest doesn't install OSD packages when using fstype=mem
            timday Tim Day added a comment -

            It looks the packages are being installed now. Thanks! lustre-initialization still fails, but that's because of bugs in my patch.

            timday Tim Day added a comment - It looks the packages are being installed now. Thanks! lustre-initialization still fails, but that's because of bugs in my patch.
            colmstea Charlie Olmstead added a comment -

            Deployed change and retested the fstype=mem test parameter session

            colmstea Charlie Olmstead added a comment - Deployed change and retested the fstype=mem test parameter session
            gerrit Gerrit Updater added a comment -

            "Charlie Olmstead <charlie@whamcloud.com>" merged in patch https://review.whamcloud.com/c/private/autotest/+/57459/
            Subject: LU-18545 - Autotest doesn't install OSD packages when using fstype=mem
            Project: private/autotest
            Branch: master
            Current Patch Set:
            Commit: 618ff3af73a279a2b0147fef6c9b26b63d24ff67

            gerrit Gerrit Updater added a comment - "Charlie Olmstead <charlie@whamcloud.com>" merged in patch https://review.whamcloud.com/c/private/autotest/+/57459/ Subject: LU-18545 - Autotest doesn't install OSD packages when using fstype=mem Project: private/autotest Branch: master Current Patch Set: Commit: 618ff3af73a279a2b0147fef6c9b26b63d24ff67
            gerrit Gerrit Updater added a comment -

            "Charlie Olmstead <charlie@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/c/private/autotest/+/57459
            Subject: LU-18545 - Autotest doesn't install OSD packages when using fstype=mem
            Project: private/autotest
            Branch: master
            Current Patch Set: 1
            Commit: ef3522445a3944692ac39d9f683c112635a1a0d2

            gerrit Gerrit Updater added a comment - "Charlie Olmstead <charlie@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/c/private/autotest/+/57459 Subject: LU-18545 - Autotest doesn't install OSD packages when using fstype=mem Project: private/autotest Branch: master Current Patch Set: 1 Commit: ef3522445a3944692ac39d9f683c112635a1a0d2
            adilger Andreas Dilger added a comment -

            colmstea, could you or Lee please take a look at this. I'm guessing there is some autotest/ljb mechanics for handling the fstype=NNN test parameter that is not understanding the use of "fstype=mem" in this case?

            adilger Andreas Dilger added a comment - colmstea , could you or Lee please take a look at this. I'm guessing there is some autotest/ljb mechanics for handling the fstype=NNN test parameter that is not understanding the use of " fstype=mem " in this case?

            People

              colmstea Charlie Olmstead
              timday Tim Day
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: