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

Errors when setting a custom time range in Observe Logs from OCP Console

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • Logging 5.8.0
    • Logging 5.7.6
    • Log Console
    • None
    • False
    • None
    • False
    • NEW
    • VERIFIED
    • Before this update, selecting a date in the time range modal for logs caused a browser error. With this update, selecting a date causes no error.
    • Bug Fix
    • Moderate

      Description of problem:

      When going to Observe > Logs and trying to set a "Custom time range" changing the day, it's returned one of the following error:

1)"Oh no! Something went wrong."

TypeError

Description
e is null

2)"Oh no! Something went wrong." 

TypeError 

Description
e.split is not a function

The "Component trace" and "Stack trace" will be attached

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

      OCP 4.13
Loki 5.7.6
CLO 5.7.6

      How reproducible:

      Always

      Steps to Reproduce:

      1. Install Loki integrated with OCP Console
2. Go to Observe > Logs and set a "Custom time range" changing the day from the "From" or "To" boxes

      Actual results:

      An "e is null" error is returned
An "e.split is not a function" error is returned

      Expected results:

      Not error is returned and able to see the logs from the custom time range

      Additional info:

       

       

              gbernal@redhat.com Gabriel Bernal
              rhn-support-ocasalsa Oscar Casal Sanchez
              Giriyamma Karagere Ramaswamy Giriyamma Karagere Ramaswamy (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: