Bug 2223705 - Fix the time selection dropdown issue for the ceph RBD snapshot graph in DR dashboard
Summary: Fix the time selection dropdown issue for the ceph RBD snapshot graph in DR d...
Keywords:
Status: POST
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.14
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ODF 4.14.0
Assignee: Timothy Asir
QA Contact: kmanohar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-18 14:38 UTC by Timothy Asir
Modified: 2023-08-09 16:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage odf-console pull 935 0 None open Bug 2223705: Fix the time selection dropdown issue for the ceph RBD snapshot graph in DR dashboard 2023-08-01 05:11:18 UTC

Description Timothy Asir 2023-07-18 14:38:30 UTC
Description of problem (please be detailed as possible and provide log
snippests): Fix the time selection dropdown issue for the ceph rrd snapshot graph in DRPolicy dashboard in ACM. Every graph has a separate drop-down to select the time. In other places we have one common time selection for the graphs. Either we can have a common dropdown selection or fix the selection issue.

Version of all relevant components (if applicable):
4.14

Can this issue reproduce from the UI?
yes

Steps to Reproduce:
1. select the time by clicking the drop-drown button for the first graph
2. we can see the graph data changed according to the time selection.
3. also we can see the another graph changed according to the time selection here.


Actual results:
Graph changed based on the time selection on any drop-down

Expected results:
Either this section should have a common drop-down selection for the selected cluster or the another graph time should not changed.

Additional info:


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