-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
-
False
-
-
-
OCMUI Core Sprint 257, OCMUI Core Sprint 258, OCMUI Core Sprint 259
Description of problem:
For OSD, OCP, ROSA clusters, navigating to the cluster history tab of cluster details page it's possible to notice unclear behavior related to the application of dates filters in the queries for cluster logs made by UI to the back-end.
On the page loading at least one query is executed, applying any filter date (although in case of OCP and OSD 2 or more queries are actually executed, on query contains a filter or the date being after one month ago, or creation date, if it's more recent). From UX point of view probably this is a first issue, because in the tab, the user can see the date filter components showing "last month", instead you get all the logs related to clusters, including the ones older than one month, if any.
About the second issue: if the user apply some filter, for example "severity", a new query is launched but this time, a date filter is added. The date filter added is "last month", or "after creation date" if it's more recent. If the user clicks on "clear filters", then if he try to apply again any other filter, the corresponding query won't include any dates filter anymore.
To actually apply the last month filter again, the user should click on the date range menu entry corresponding to "last month" (although it's shown as already selected). Then any next filter application, for example severity, will trigger a query including the "last month" filter again (in addition to severity).
To summarize, the first issue could be solved applying the "last month" filter in the initial query. The second issue could be solved fixing the action related to the "clear filters" link which in a certain way remove the dates filter from any future query.
How reproducible:
always
Steps to Reproduce:
- Open OCM UI staging.
- Go to cluster details page of an OSD, ROSA or OCP cluster
- Go to cluster history tab
- Observe the network tab of the developer tools panel or just observe the cluster logs shown in the page
- Apply some filter (for example severity)
- Observe the network tab of the developer tools panel or just observe the cluster logs shown in the page
- Click on the "clear filters" link
- Apply again some filter
- Observe the network tab of the developer tools panel or just observe the cluster logs shown in the page
Actual results:
At step 4 you can observe as the query launched by UI doesn't contain any date filter although in the page, the "last month" filter seems to be selected.
At step 9 you can notice as the query launched by UI doesn't contain any date filter although in the page which is at odds with step 6.
Screencast from 2024-07-31 11-09-29.webm
Expected results:
In step 4 the query should include the "last month" filter.
In step 9 the query should include the "last month" filter.
- incorporates
-
OCMUI-2570 [Cluster history] The date filters were not reset when a new cluster definition opened from OCM UI
- Closed
- is blocked by
-
OCMUI-2284 Unnecessary re-renders in Cluster details > Cluster history tab
- Closed
- is related to
-
OCMUI-1306 [OCM UI QE] Create test case automation for day2 cluster history operations for ROSA classic cluster.
- To Do
- relates to
-
OCMUI-2067 [OCM UI] cluster details: history filter "logged by/description" leads back-end to be unresponsive
- Closed
- mentioned on