Bug 1997079 - Custom time range not working
Summary: Custom time range not working
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.9.0
Assignee: Vikram Raj
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-24 11:41 UTC by Vikram Raj
Modified: 2021-10-18 17:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 17:48:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 9863 0 None None None 2021-08-24 11:42:10 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:48:37 UTC

Description Vikram Raj 2021-08-24 11:41:17 UTC
Description of problem:
The custom time range in the monitoring dashboard doesn't seem to be working

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


How reproducible:


Steps to Reproduce:
1.enter a custom time range in the time range dropdown

Actual results:
The graphs are not updated according to the custom time range

Expected results:
The graphs should update according to the time range

Additional info:
Build - 4.9.0-0.nightly-2021-08-22-005117

Comment 3 Mohammed Saud 2021-08-30 12:49:16 UTC
Verified on:
Build: 4.9.0-0.nightly-2021-08-29-010334
Browser: Firefox 91

Comment 7 errata-xmlrpc 2021-10-18 17:48:10 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.9.0 bug fix and 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-2021:3759


Note You need to log in before you can comment on or make changes to this bug.