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

[release-5.7] Custom time range is not getting updated on Aggregated Logs page

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • VERIFIED
    • Before this update, selecting a time range by dragging over the histogram didn't work on the aggregated logs view inside the pod detail. After this update the time range can be selected by dragging on the histogram in this view.
    • Bug Fix

      Description of problem:

      On the Aggregated Logs page inside a Pod details tab, Custom time range is not getting updated if select with cursor move on the histogram.

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

      Logging: 5.7

      How reproducible:

      Always

      Steps to reproduce:

      1. Deploy OpenShift Logging 5.7 with Loki/Vector stack and enable Logging console plugin according to https://docs.openshift.com/container-platform/4.12/logging/cluster-logging-loki.html#logging-loki-deploy_cluster-logging-loki 
      2. Deploy some application pod 
      3. Search logs from OpenShift webconsole's Admin > Observe >  Logs 
      4. Click on the "Show Resource", then click on the link to pods page
      5. Try the cursor move option to select custom time range on the Histogram 

      Actual results:

      Custom time is not update 

      Expected results:

      Custom time range is updated

        1. Screenshot 2023-07-11 at 2.57.18 PM.png
          Screenshot 2023-07-11 at 2.57.18 PM.png
          257 kB

            [LOG-4108] [release-5.7] Custom time range is not getting updated on Aggregated Logs page

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Moderate: Logging Subsystem 5.7.3 - Red Hat OpenShift security update), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHSA-2023:3998

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Moderate: Logging Subsystem 5.7.3 - Red Hat OpenShift security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:3998

            Kabir Bharti added a comment -

            Verified on cluster-logging.v5.7.3

            Kabir Bharti added a comment - Verified on cluster-logging.v5.7.3

            GitLab CEE Bot added a comment -

            CPaaS Service Account mentioned this issue in a merge request of openshift-logging / Log Collection Midstream on branch openshift-logging-5.7-rhel-8_upstream_80b3c6bea4bb60826f0a8205d7c5e04a:

            Updated 2 upstream sources

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in a merge request of openshift-logging / Log Collection Midstream on branch openshift-logging-5.7-rhel-8_ upstream _80b3c6bea4bb60826f0a8205d7c5e04a : Updated 2 upstream sources

              gbernal@redhat.com Gabriel Bernal
              gkarager Giriyamma Karagere Ramaswamy (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: