Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Normal
Fix Version/s: Logging 5.6.5
Affects Version/s: Logging 5.6.1
Component/s: Log Console
Labels:
- devel_ack+

Blocked:
False
Blocked Reason:
None
Ready:
False
Docs QE Status:
NEW
QE Status:
VERIFIED
Release Note Text:

Hide
Before this update, the selection of an invalid time range format was allowed, preventing the user from selecting a valid range. With this update, time formats are now validated, enabling users to select a valid range. If an invalid time range format is selected, an error message is displayed to the user.

Show
Before this update, the selection of an invalid time range format was allowed, preventing the user from selecting a valid range. With this update, time formats are now validated, enabling users to select a valid range. If an invalid time range format is selected, an error message is displayed to the user.
Intelligence Requested:
Market:

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

$ oc get csv
NAME DISPLAY VERSION REPLACES PHASE
cluster-logging.v5.6.1 Red Hat OpenShift Logging 5.6.1 Succeeded
loki-operator.v5.6.1 Loki Operator 5.6.1 Succeeded

1. Seeing "Invalid date range" error after setting custom time range by selecting the time from drop down.
Steps to reproduce: 1. Set time range by selecting the time from drop down, save
2. Open the Custom time range window

2. Sometimes, result for both graph and logs table is not consistent when the log count is 1.
Steps to reproduce: 1. Select single log entry from the graph by dragging option.