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

Loki buildinfo is obscured

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • Logging 5.9.0
    • Logging 5.6.16, Logging 5.7.11, Logging 5.8.4, Logging 5.9.0
    • Log Storage
    • False
    • None
    • False
    • NEW
    • NEW
    • Hide
      Before this update, the Red Hat build pipeline did not apply existing build information to Loki builds caused an the Loki buildinfo API missing that info (e.g. revision, branch, version). With this update, the Red Hat build pipeline populates these inputs into the Loki build resolves the issue.
      Show
      Before this update, the Red Hat build pipeline did not apply existing build information to Loki builds caused an the Loki buildinfo API missing that info (e.g. revision, branch, version). With this update, the Red Hat build pipeline populates these inputs into the Loki build resolves the issue.
    • Release Note Not Required
    • Log Storage - Sprint 250, Log Storage - Sprint 251
    • Informational

      Description of problem:

      Customer wanted to check the Loki version we use in our distribution to help with some external integration. However it seems to be obscured when checked internally:

      $ curl -k https://localhost:3101/loki/api/v1/status/buildinfo
      {"version":"","revision":"","branch":"","buildUser":"","buildDate":"","goVersion":""}
      

      Although the information is public in the Dockerfile:

      commit 8ce8168739bf629bd44f89f095b8705edf82a507 (origin/upstream-v2.9.4)
      

      Version-Release number of selected component (if applicable):

      Verified on OpenShift Logging 5.8.4

      How reproducible:

      Reproduced on 5.8.4

      Steps to Reproduce:

      $ oc rsh logging-loki-distributor-75c4864cc5-ln4m7
      $ curl -k https://localhost:3101/loki/api/v1/status/buildinfo
      {"version":"","revision":"","branch":"","buildUser":"","buildDate":"","goVersion":""}
      
      

      While this is not a major/breaking issue, it can affect usability for integration with other processes and isn't "open"

              ptsiraki@redhat.com Periklis Tsirakidis
              rhn-support-stwalter Steven Walter
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: