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

build failures on SLES

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • Lustre 2.9.0
    • None
    • None
    • 3
    • 9223372036854775807

    Description

      The recent rpm naming and build changes due to LU-5614 that landed recently appear to interact badly with kernel builds on SLES.
      In particular on a recent build for sles12 it generates lustre rpms where the Provides strings in the lustre-kmp rpms don't match the Requires strings in the other lustre rpms. This prevents normal installs from completing. Only installs with --nodeps or --force options works.

      examples:

      # rpm -ivh lustre-kmp-default-2* lustre-osd-ldiskfs-kmp-default-2*
      lustre-osd-ldiskfs-mount-2* lustre-2* lustre-iok* lustre-tests-kmp-default-2*
      lustre-tests-2*
      error: Failed dependencies:
      	lustre-kmp = 2.8.55_27_g35038f0_3.12.59_60.41_lustre is needed by
      lustre-osd-ldiskfs-kmp-default-2.8.55_27_g35038f0_k3.12.59_60.41-3.12.59_60.41_
      lustre_default.x86_64
      	lustre-kmp = 2.8.55_27_g35038f0_3.12.59_60.41_lustre is needed by
      lustre-2.8.55_27_g35038f0-3.12.59_60.41_lustre_default.x86_64
      	lustre-kmp = 2.8.55_27_g35038f0_3.12.59_60.41_lustre is needed by
      lustre-tests-2.8.55_27_g35038f0-3.12.59_60.41_lustre_default.x86_64
      

      looking at the Provides in the lustre-kmp-default rpm shows:

      lustre-kmp = 2.8.55_27_g35038f0_k3.12.59_60.41

      while the Requires string needed in the lustre rpms can be seen to be:

      2.8.55_27_g35038f0_3.12.59_60.41_lustre

      in the error messages above.
      Looks like there's an extra 'k' character in the string "2.8.55_27_g35038f0_k3.12.59_60.41" that's blocking a good match.
      Think it should probably say "..._g35038f0_3.12.59_60.41" not "_g35038f0_k3.12.59_60.41" as it does now.

      Attachments

        Issue Links

          Activity

            People

              mdiep Minh Diep
              bogl Bob Glossman (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: