Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-5276

[release-5.6] expose buildDate, goVersion in Loki buildinfo

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done-Errata
    • Minor
    • Logging 5.6.17
    • Logging 5.7.12, Logging 5.8.5, Logging 5.9.0
    • Log Storage
    • False
    • None
    • False
    • NEW
    • NEW
    • Before this update, the build pipeline missed to add linker flags for build date caused Loki builds to report empty strings for build date and goVersion. With this update, the build pipeline adds missing linker flags resolves the issue.
    • Bug Fix
    • Log Storage - Sprint 251

    Description

      Description of problem:

      buildDate,builduser and goVersion are not exposed in buildinfo. Can we expose these infos?

      curl -k https://localhost:3101/loki/api/v1/status/buildinfo

      {"version":"v2.9.4","revision":"8ce8168","branch":"upstream-v2.9.4","buildUser":"","buildDate":"","goVersion":""}

      By the way, there are some build info image label

        "build-date": "2024-03-11T15:26:47",
  "io.buildah.version": "1.29.0",
  "io.openshift.build.commit.id": "8ce8168739bf629bd44f89f095b8705edf82a507",
  "release": "13",
  "summary": "Provides the latest release of Red Hat Universal Base Image 9.",
  "url": "https://access.redhat.com/containers/#/registry.access.redhat.com/openshift-logging/logging-loki-rhel9/images/v2.9.4-13",
  "vendor": "Red Hat, Inc.",
  "version": "v2.9.4"

      .....

      Steps to Reproduce:

      1. oc exec <loki-pod> – curl -k https://localhost:3101/loki/api/v1/status/buildinfo
      3. ...

      Actual results:

      Expected results:

      Additional info:

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. LOG-5261 expose buildDate, goVersion in Loki buildinfo

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          links to

          Web Link RHSA-2024:127993 Logging for Red Hat OpenShift - 5.6.17

          Activity

            People

              ptsiraki@redhat.com Periklis Tsirakidis
              rhn-support-anli Anping Li
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: