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

Avoid `uname -r` usage during configure when the LINUIX[_OBJ] have already been handled

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • None
    • None
    • None
    • 3
    • 9223372036854775807

    Description

      In a container 'uname -r' reports the 'wrong value', instead we should use the kernel version that is being configured: $UTS_RELEASE

      While lustre cannot be mounted from within a container, however it can be built in one.

      Attachments

        Issue Links

          Activity

            [LU-17813] Avoid `uname -r` usage during configure when the LINUIX[_OBJ] have already been handled

            Resolve as duplicate of LU-16819

            stancheff Shaun Tancheff added a comment - Resolve as duplicate of LU-16819
            gerrit Gerrit Updater added a comment - - edited

            "Shaun Tancheff <shaun.tancheff@hpe.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/55010
            Subject: LU-17813 build: prefer UTS_RELEASE over uname -r
            Project: fs/lustre-release
            Branch: master
            Current Patch Set: 1
            Commit: 0a378c55f40ad27f77d0b82adc926d31c4b0c174

            gerrit Gerrit Updater added a comment - - edited "Shaun Tancheff <shaun.tancheff@hpe.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/55010 Subject: LU-17813 build: prefer UTS_RELEASE over uname -r Project: fs/lustre-release Branch: master Current Patch Set: 1 Commit: 0a378c55f40ad27f77d0b82adc926d31c4b0c174

            People

              stancheff Shaun Tancheff
              stancheff Shaun Tancheff
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: