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

lustre-master build versions are useless

Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • Lustre 2.4.0
    • None
    • 3
    • 7944

    Description

      The build version reported for "lustre-master" builds is completely useless:

      https://maloo.whamcloud.com/test_sessions/2d999b0a-add9-11e2-b72d-52540035b04c

      Lustre Version:	jenkins-arch=x86_64,build_type=server,distro=el6,ib_stack=inkern
      Lustre Version:	jenkins-arch=x86_64,build_type=client,distro=el6,ib_stack=inkern
      

      I suspect this string is coming from the "lctl lustre_build_version" command, and the version itself is being set by the lbuild script? Sorry, I don't know the full details, just that it is not useful as is.

      Attachments

        Issue Links

          Activity

            [LU-3237] lustre-master build versions are useless

            This was fixed at some point.

            adilger Andreas Dilger added a comment - This was fixed at some point.

            Does anyone understand where these bogus/useless version strings are coming from? I looked at lustre/scripts/version_tag-git.pl and couldn't see where it is coming from. I'm trying to understand some interoperability test results, but looking at the Maloo test page doesn't tell me a lot:

            Version(s):    jenkins-arch=x86_64,build_type=server,distro=el6,ib_stack=inkern (x86_64)
                           jenkins-g6ab50e8-PRISTINE-2.6.32-279.19.1.el6.x86_64 (x86_64)
            

            Yes, it is possible to find out the approximate versions (master and b2_1) by looking at the test session, but it would be far more useful to have something with the Lustre version, the commit hash, and the build number:

            Client Version: v2_1_5_0-g643e972a0e-197 (x86_64)
            Server Version: v2_3_65_0-6-gg6ab50e8-15392 (x86_64)
            

            All of the other information can be extracted from those labels as needed.

            adilger Andreas Dilger added a comment - Does anyone understand where these bogus/useless version strings are coming from? I looked at lustre/scripts/version_tag-git.pl and couldn't see where it is coming from. I'm trying to understand some interoperability test results, but looking at the Maloo test page doesn't tell me a lot: Version(s): jenkins-arch=x86_64,build_type=server,distro=el6,ib_stack=inkern (x86_64) jenkins-g6ab50e8-PRISTINE-2.6.32-279.19.1.el6.x86_64 (x86_64) Yes, it is possible to find out the approximate versions (master and b2_1) by looking at the test session, but it would be far more useful to have something with the Lustre version, the commit hash, and the build number: Client Version: v2_1_5_0-g643e972a0e-197 (x86_64) Server Version: v2_3_65_0-6-gg6ab50e8-15392 (x86_64) All of the other information can be extracted from those labels as needed.

            People

              wc-triage WC Triage
              adilger Andreas Dilger
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: