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

Handle LU-4606 packaging changes for Lustre Server DKMS RPM

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • Lustre 2.7.0
    • None
    • 3
    • 16382

    Description

      LU-4606 has introduced some packaging changes and particularly one that causes a lib/dso to be shipped inside each of the lustre-osd RPMs.
      This breaks current packaging of Lustre Server DKMS RPM which presently builds and provides the osd module but also conflicts with the lustre-osd package!
      This leads to the Lustre Server DKMS RPM to be unusable due to the necessary lib/dso for the mount command not to be installed.

      Attachments

        Issue Links

          Activity

            [LU-5851] Handle LU-4606 packaging changes for Lustre Server DKMS RPM
            adilger Andreas Dilger made changes -
            Link New: This issue is duplicated by INTL-140 [ INTL-140 ]
            pjones Peter Jones made changes -
            Labels Original: 22i HB New: HB
            jlevi Jodi Levi (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Patches have landed to Master. Please reopen ticket if more work is still needed.

            jlevi Jodi Levi (Inactive) added a comment - Patches have landed to Master. Please reopen ticket if more work is still needed.
            bfaccini Bruno Faccini (Inactive) added a comment - Option #1 ( http://review.whamcloud.com/12538 ) and #2 ( http://review.whamcloud.com/12550 ) patches have been abandoned.

            Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/12589/
            Subject: LU-5851 build: split lustre-osd RPMs
            Project: fs/lustre-release
            Branch: master
            Current Patch Set:
            Commit: 2aa189790ca95f0f4f1d32fadea3269080091b02

            gerrit Gerrit Updater added a comment - Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/12589/ Subject: LU-5851 build: split lustre-osd RPMs Project: fs/lustre-release Branch: master Current Patch Set: Commit: 2aa189790ca95f0f4f1d32fadea3269080091b02

            Nathaniel, thanks I think you are right unfortunately and that my testing environment for Option 2 / 12550 was incomplete+wrong and was hiding the libzfs dependency of mount_osd_zfs.so lib. BTW, auto-tests did not trigger it too which may mean that no pure ldiskfs Server install is made during non zfs-reviews?
            So since, I easily presume it will not be accepted to revert some of your changes from LU-4606 and switch-back to the method where libzfs is dlopen()'ed in mount_utils_zfs.c instead of being explicitely linked now nor to use, since Option 1 / 12538 has already been abandonned, you are again right there is only Option 3 / 12589 left, unless there is some other and better idea to fix?

            bfaccini Bruno Faccini (Inactive) added a comment - Nathaniel, thanks I think you are right unfortunately and that my testing environment for Option 2 / 12550 was incomplete+wrong and was hiding the libzfs dependency of mount_osd_zfs.so lib. BTW, auto-tests did not trigger it too which may mean that no pure ldiskfs Server install is made during non zfs-reviews? So since, I easily presume it will not be accepted to revert some of your changes from LU-4606 and switch-back to the method where libzfs is dlopen()'ed in mount_utils_zfs.c instead of being explicitely linked now nor to use, since Option 1 / 12538 has already been abandonned, you are again right there is only Option 3 / 12589 left, unless there is some other and better idea to fix?

            Option 2 / 12550 causes a zfs dependency in the base lustre rpm, and I would think that that would cause large headaches for ldiskfs only sites.
            Option 3 (seperate user-space rpms with the dso's) seems like the right answer

            utopiabound Nathaniel Clark added a comment - Option 2 / 12550 causes a zfs dependency in the base lustre rpm, and I would think that that would cause large headaches for ldiskfs only sites. Option 3 (seperate user-space rpms with the dso's) seems like the right answer
            adilger Andreas Dilger made changes -
            Link New: This issue is related to LU-6013 [ LU-6013 ]

            Option 2, change 12550, seems like the best stop-gap measure as of version Patch Set 6. I marked it -1 but my quibbles are pretty minor and easily addressed.

            Longer term, we really need to address some a bigger issue with this code, but it doesn't really need to be addressed in this ticket:

            We shouldn't call osd_init() at all for client mounts. Better yet, maybe we should split the server mounts out into a separate mount command, e.g. mount.lustre_server. Or maybe even one for each osd type: mount.losd_zfs, mount.losd_ldiskfs.

            morrone Christopher Morrone (Inactive) added a comment - Option 2, change 12550 , seems like the best stop-gap measure as of version Patch Set 6. I marked it -1 but my quibbles are pretty minor and easily addressed. Longer term, we really need to address some a bigger issue with this code, but it doesn't really need to be addressed in this ticket: We shouldn't call osd_init() at all for client mounts. Better yet, maybe we should split the server mounts out into a separate mount command, e.g. mount.lustre_server. Or maybe even one for each osd type: mount.losd_zfs, mount.losd_ldiskfs.

            People

              bfaccini Bruno Faccini (Inactive)
              bfaccini Bruno Faccini (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: