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

[release-5.8] Console label queries should use Loki API instead of k8s API

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • Logging 5.8.9
    • Logging 5.8.z, Logging 5.9.z
    • Log Console
    • False
    • None
    • False
    • NEW
    • NEW
    • Fixed an issue which prevented pods from being selectable if they no longer exist, even if they had generated logs.
    • Bug Fix

      Description of problem:

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

      5.8

      How reproducible:

      Always

      Steps to Reproduce:

      1. With LokiStack and CLO installed
      2. Navigate to the admin console logs
      3. Try to select from the dropdown pods that created log entries but no longer exists (e.g. deployment restart rollout)

      Actual results:

      Pods that no longer exist are not listed even if they generated logs in the selected time range

      Expected results:

      Pods that generated logs are included in the dropdown so the log data can be listed

      Additional info:

       

      The dev console already uses the Loki API due to namespaces permission

            rh-ee-pyurkovi Peter Yurkovich
            gbernal@redhat.com Gabriel Bernal
            Anping Li Anping Li
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: